Re: [patch V2] mm/slub: Move slab initialization into irq enabled region

2015-07-15 Thread David Rientjes
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

Re: [patch V2] mm/slub: Move slab initialization into irq enabled region

2015-07-10 Thread Christoph Lameter
Acked-by: Christoph Lameter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[patch V2] mm/slub: Move slab initialization into irq enabled region

2015-07-10 Thread Thomas Gleixner
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 p