On Wed, 26 Sep 2012, David Rientjes wrote: > On Wed, 26 Sep 2012, Christoph Lameter wrote: > > > > Nack, this is already handled by CREATE_MASK in the mm/slab.c allocator; > > > > CREATE_MASK defines legal flags that can be specified. Other flags cause > > and error. This is about flags that are internal that should be ignored > > when specified. > > > > That should be ignored for the mm/slab.c allocator, yes. Then you are ok with the patch as is? > > I think it makes sense to reserve some top flags for internal purposes. > > > > It depends on the implementation: if another slab allocator were to use > additional bits that would be a no-op with mm/slab.c, then this patch > would be too restrictive. There's also no requirement that any "internal > flags" reserved by a slab allocator implementation must be shared in the > same kmem_cache field as the flags passed to kmem_cache_create() -- it's > actually better if they aren't since they seldom need to be accessed in > the same cacheline. There *are* multiple slab allocators using those bits! And this works for them. There is nothing too restrictive here. The internal flags are standardized by this patch to be in the highest nibble. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>