From: Bodo Eggert <harvested.in.lkml@7eggert.dyndns.org>
To: balbir@in.ibm.com, Pekka Enberg <penberg@cs.helsinki.fi>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slab: introduce kmem_cache_zalloc allocator
Date: Mon, 20 Mar 2006 20:07:59 +0100 [thread overview]
Message-ID: <E1FLPjT-0000o9-Sy@be1.lrz> (raw)
In-Reply-To: <5SvK8-88q-41@gated-at.bofh.it>
Balbir Singh <balbir@in.ibm.com> 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.
next parent reply other threads:[~2006-03-20 19:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5Ssjj-314-69@gated-at.bofh.it>
[not found] ` <5Sv7o-7l5-23@gated-at.bofh.it>
[not found] ` <5Svh9-7xW-61@gated-at.bofh.it>
[not found] ` <5SvK8-88q-41@gated-at.bofh.it>
2006-03-20 19:07 ` Bodo Eggert [this message]
2006-03-21 3:25 ` Balbir Singh
2006-03-21 10:51 ` Bodo Eggert
2006-03-21 11:32 ` Pekka J Enberg
2006-03-20 13:07 Pekka J Enberg
2006-03-20 13:51 ` Eric Dumazet
2006-03-20 14:21 ` Pekka J Enberg
2006-03-20 16:05 ` Balbir Singh
2006-03-20 16:14 ` Pekka Enberg
2006-03-20 16:45 ` Balbir Singh
2006-03-21 7:13 ` Pekka J Enberg
2006-03-21 10:36 ` Andrew Morton
2006-03-21 11:03 ` Pekka J Enberg
2006-03-21 18:35 ` Manfred Spraul
2006-03-21 18:37 ` Pekka Enberg
2006-03-21 11:25 ` Andrew Morton
2006-03-21 11:50 ` Pekka J Enberg
2006-03-21 16:30 ` Pekka Enberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1FLPjT-0000o9-Sy@be1.lrz \
--to=harvested.in.lkml@7eggert.dyndns.org \
--cc=7eggert@gmx.de \
--cc=akpm@osdl.org \
--cc=balbir@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome