On Wed, 17 Oct 2012 15:36:51 +0400 Glauber Costa <glommer@xxxxxxxxxxxxx> wrote: > Some flags are used internally by the allocators for management > purposes. One example of that is the CFLGS_OFF_SLAB flag that slab uses > to mark that the metadata for that cache is stored outside of the slab. > > No cache should ever pass those as a creation flags. We can just ignore > this bit if it happens to be passed (such as when duplicating a cache in > the kmem memcg patches). I may be minunderstanding this, but... If some caller to kmem_cache_create() is passing in bogus flags then that's a bug, and it is undesirable to hide such a bug in this fashion? > Because such flags can vary from allocator to allocator, we allow them > to make their own decisions on that, defining SLAB_AVAILABLE_FLAGS with > all flags that are valid at creation time. Allocators that doesn't have > any specific flag requirement should define that to mean all flags. > > Common code will mask out all flags not belonging to that set. -- 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>