Balbir Singh <[email protected]> wrote:
>> No, no, no! I am introducing kmem_cache_zalloc() because there are
>> existing users in the tree. I plan to kill the slab wrappers from XFS
>> completely which is why I need this. We already have object constructors
>> for what you're describing.
>
> 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.
--
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.
-
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/
[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]
