On Thu, 21 Jun 2012, Glauber Costa wrote: > During kmem_cache_init_late(), we transition to the LATE state, > and after some more work, to the FULL state, its last state > > This is quite different from slub, that will only transition to > its last state (previously SYSFS), in a (late)initcall, after a lot > more of the kernel is ready. > > This means that in slab, we have no way to taking actions dependent > on the initialization of other pieces of the kernel that are supposed > to start way after kmem_init_late(), such as cgroups initialization. > > To achieve more consistency in this behavior, that patch only > transitions to the UP state in kmem_init_late. In my analysis, > setup_cpu_cache() should be happy to test for >= UP, instead of > == FULL. It also has passed some tests I've made. > > We then only mark FULL state after the reap timers are in place, > meaning that no further setup is expected. > > Signed-off-by: Glauber Costa <glommer@xxxxxxxxxxxxx> > Acked-by: Christoph Lameter <cl@xxxxxxxxx> > CC: Pekka Enberg <penberg@xxxxxxxxxxxxxx> > CC: David Rientjes <rientjes@xxxxxxxxxx> Acked-by: David Rientjes <rientjes@xxxxxxxxxx> [ Might want to fix your address book in your email client because Christoph's name is misspelled in the cc list. ] -- 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>