| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <87abdz84d2.wl%peter@chubb.wattle.id.au> Date: Tue, 23 Sep 2008 21:54:17 +1000 From: peter@...bb.wattle.id.au To: Nick Piggin <npiggin@...e.de> Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>, Jeremy Fitzhardinge <jeremy@...p.org>, Linux Memory Management List <linux-mm@...ck.org>, Linux Kernel list <linux-kernel@...r.kernel.org>, Hugh Dickins <hugh@...itas.com> Subject: Re: PTE access rules & abstraction >>>>> "Nick" == Nick Piggin <npiggin@...e.de> writes: Nick> On Tue, Sep 23, 2008 at 04:49:32PM +1000, Benjamin Herrenschmidt Nick> wrote: >> > What is the complete set of primitives we need? I also noticed >> that a > number of the existing pagetable operations are used only >> once or twice > in the core code; I wonder if we really need such >> special cases, or > whether we can make each arch pte operation >> carry a bit more weight? >> >> Yes, that was some of my concern. It's getting close to having one >> API per call site :-) Nick> I don't think that is a huge problem as such... if there was Nick> lots of repeated uses of the API I'd also be concerned about mm/ Nick> code not being well factored :) Is it worth taking another look at the page-table abstraction layer that Darren Williams posted here last year? PeterC -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists