Re: [patch 07/10] SLUB: Avoid referencing kmem_cache structure in __slab_alloc

On Sat, 27 Oct 2007, Christoph Lameter wrote:
> There is the need to use the objects per slab in the first part of
> __slab_alloc() which is still pretty hot. Copy the number of objects
> per slab into the kmem_cache_cpu structure. That way we can get the
> value from a cache line that we already need to touch. This brings
> the kmem_cache_cpu structure up to 4 even words.

Reviewed-by: Pekka Enberg <[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/

---

• References:
  • [patch 00/10] SLUB: SMP regression tests on Dual Xeon E5345 (8p) and new performance patches
    • From: Christoph Lameter <[email protected]>
  • [patch 07/10] SLUB: Avoid referencing kmem_cache structure in __slab_alloc
    • From: Christoph Lameter <[email protected]>

• Prev by Date: Re: [patch 05/10] SLUB: __slab_alloc() exit path consolidation
• Next by Date: Re: USB_SUSPEND needs SUSPEND?
• Previous by thread: [patch 07/10] SLUB: Avoid referencing kmem_cache structure in __slab_alloc
• Next by thread: Re: [patch 07/10] SLUB: Avoid referencing kmem_cache structure in __slab_alloc
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]