Re: [patch 04/10] SLUB: Avoid checking for a valid object before zeroing on the fast path

On Sat, 27 Oct 2007, Christoph Lameter wrote:
> The fast path always results in a valid object. Move the check
> for the NULL pointer to the slow branch that calls
> __slab_alloc. Only __slab_alloc can return NULL if there is no
> memory available anymore and that case is exceedingly rare.

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 04/10] SLUB: Avoid checking for a valid object before zeroing on the fast path
  - From: Christoph Lameter <[email protected]>

Prev by Date: Re: [PATCH] proc_fs.h redux
Next by Date: Re: [patch 05/10] SLUB: __slab_alloc() exit path consolidation
Previous by thread: [patch 04/10] SLUB: Avoid checking for a valid object before zeroing on the fast path
Next by thread: [patch 06/10] SLUB: Provide unique end marker for each slab
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]