Re: [PATCH] slab: introduce kmem_cache_zalloc allocator

> > Ok, please keep the interface - build kmem_cache_zalloc() on top of
> > what I suggest.
> 
> The benefit of using *zalloc is the ability to skip the memset by using
> pre-zeroed memory or to use more efficient ways of zeroing a page.
> Having to check the value of a parameter wouldn't help.

Hmm... the current patch directly does a memset(). Are you talking about
possible optimizations to kmem_cache_zalloc()?

Balbir
-
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/

---

• Follow-Ups:
  • Re: [PATCH] slab: introduce kmem_cache_zalloc allocator
    • From: Bodo Eggert <[email protected]>

• References:
  • Re: [PATCH] slab: introduce kmem_cache_zalloc allocator
    • From: Bodo Eggert <[email protected]>

• Prev by Date: Re: nommu_map_sg: overflow with ata_piix?
• Next by Date: [2.6.16 STABLE PATCH] V4L/DVB (3324): Fix Samsung tuner frequency ranges
• Previous by thread: Re: [PATCH] slab: introduce kmem_cache_zalloc allocator
• Next by thread: Re: [PATCH] slab: introduce kmem_cache_zalloc allocator
• 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]