Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030192AbWAXHXL (ORCPT ); Tue, 24 Jan 2006 02:23:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030193AbWAXHXK (ORCPT ); Tue, 24 Jan 2006 02:23:10 -0500 Received: from ns1.suse.de ([195.135.220.2]:28594 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S1030192AbWAXHXJ (ORCPT ); Tue, 24 Jan 2006 02:23:09 -0500 From: Andi Kleen To: Arjan van de Ven Subject: Re: [PATCH/RFC] Shared page tables Date: Tue, 24 Jan 2006 08:18:27 +0100 User-Agent: KMail/1.8.2 Cc: Ray Bryant , Dave McCracken , Robin Holt , Hugh Dickins , Linux Kernel , Linux Memory Management References: <200601240210.04337.ak@suse.de> <1138086398.2977.19.camel@laptopd505.fenrus.org> In-Reply-To: <1138086398.2977.19.camel@laptopd505.fenrus.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601240818.28696.ak@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1623 Lines: 42 On Tuesday 24 January 2006 08:06, Arjan van de Ven wrote: > > > The randomization is not for cache coloring, but for security purposes > > (except for the old very small stack randomization that was used > > to avoid conflicts on HyperThreaded CPUs). I would be surprised if the > > mmap made much difference because it's page aligned and at least > > on x86 the L2 and larger caches are usually PI. > > randomization to a large degree is more important between machines than > within the same machine (except for setuid stuff but lets call that a > special category for now). Imo prelink is one of the better bets to get > "all code for a binary/lib on the same 2 mb page", Probably yes. > all distros ship > prelink nowadays anyway SUSE doesn't use it. > (it's too much of a win that nobody can afford > to not ship it ;) KDE and some other people disagree on that. > and within prelink the balance between randomization > for security and 2Mb sharing can be struck best. In fact it needs know > about the 2Mb thing anyway to place it there properly and for all > binaries... the kernel just can't do that. Well, we first have to figure out if the shared page tables are really worth all the ugly code, nasty locking and other problems (inefficient TLB flush etc.) I personally would prefer to make large pages work better before going down that path. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/