| 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: <00000142de5634af-f92870a7-efe2-45cd-b50d-a6fbdf3b353c-000000@email.amazonses.com> Date: Tue, 10 Dec 2013 21:07:40 +0000 From: Christoph Lameter <cl@...ux.com> To: Dave Hansen <dave@...1.net> cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org, kirill.shutemov@...ux.intel.com, Andi Kleen <ak@...ux.intel.com> Subject: Re: [PATCH] [RFC] mm: slab: separate slab_page from 'struct page' On Tue, 10 Dec 2013, Dave Hansen wrote: > At least for slab, this doesn't turn out to be too big of a deal: > it's only 8 casts. slub looks like it'll be a bit more work, but > still manageable. The single page struct definitions makes it easy to see how a certain field is being used in various subsystems. If you add a field then you can see other use cases in other subsystems. If you happen to call them then you know that there is trouble afoot. Also if you screw up the sizes then you screw up the page struct for everything and its very evident that a problem exists. How do you ensure that the sizes and the locations of the fields in multiple page structs stay consistent? As far as I can tell we are trying to put everything into one page struct to keep track of the uses of various fields and to allow a reference for newcomes to the kernel. -- 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