linux-kernel - Re: [PATCH] slab: Ignore internal flags in cache creation

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 28 Sep 2012 13:39:56 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Christoph Lameter <cl@...ux.com>
cc:	Glauber Costa <glommer@...allels.com>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, Michal Hocko <mhocko@...e.cz>,
	Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: [PATCH] slab: Ignore internal flags in cache creation

On Fri, 28 Sep 2012, Christoph Lameter wrote:

> > For context, as many people who attended the kernel summit and LinuxCon
> > are aware, a new slab allocator is going to be proposed soon that actually
> > uses additional bits that aren't defined for all slab allocators.  My
> > opinion is that leaving unused bits and reserved bits to the
> > implementation is the best software engineering practice.
> 
> Could you please come out with the new allocator and post some patchsets?
> 
> We can extend the number of flags reserved if necessary but we really need
> to see the source for that.
> 

The first prototype, SLAM XP1, will be posted in October.  I'd simply like 
to avoid reverting this patch down the road and having all of us 
reconsider the topic again when clear alternatives exist that, in my 
opinion, make the code cleaner.

 [ There _was_ a field for internal flags for mm/slab.c, called "dflags", 
   before I removed it because it was unused; I'm regretting that now 
   because it would have been very easy to use it for this purpose. ]
--
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/