On Fri, 10 Jul 2015, Thomas Gleixner wrote: > Initializing a new slab can introduce rather large latencies because > most of the initialization runs always with interrupts disabled. > > There is no point in doing so. The newly allocated slab is not visible > yet, so there is no reason to protect it against concurrent alloc/free. > > Move the expensive parts of the initialization into allocate_slab(), > so for all allocations with GFP_WAIT set, interrupts are enabled. > > Signed-off-by: Thomas Gleixner <[email protected]> > Cc: Christoph Lameter <[email protected]> > Cc: Pekka Enberg <[email protected]> > Cc: David Rientjes <[email protected]> > Cc: Joonsoo Kim <[email protected]> > Cc: Andrew Morton <[email protected]> > Cc: [email protected] > Cc: Sebastian Andrzej Siewior <[email protected]> > Cc: Steven Rostedt <[email protected]> > Cc: Peter Zijlstra <[email protected]>
Acked-by: David Rientjes <[email protected]> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
