From: Pekka Enberg <penberg@cs.helsinki.fi>
To: balbir@in.ibm.com
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slab: introduce kmem_cache_zalloc allocator
Date: Mon, 20 Mar 2006 18:14:23 +0200 [thread overview]
Message-ID: <1142871263.11694.4.camel@localhost> (raw)
In-Reply-To: <20060320160500.GA25415@in.ibm.com>
On Mon, 2006-03-20 at 21:35 +0530, Balbir Singh wrote:
> Could we please create a more generic variation of this patch -- may be a
> function called kmem_cache_alloc_set(). The function would not only
> memset the data to 0, but instead to any specified pattern passed as
> an argument.
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.
On Mon, 2006-03-20 at 21:35 +0530, Balbir Singh wrote:
> This could be used to poison allocated memory. Passing 0 would make
> this equivalent to kmem_cache_zalloc(). Basically, instead of doing
I am not sure I understand what you mean. We already have slab poisoning
and that's in mm/slab.c. Why would you want to make the callers aware of
that?
Pekka
next prev parent reply other threads:[~2006-03-20 16:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 13:07 [PATCH] slab: introduce kmem_cache_zalloc allocator 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 [this message]
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
[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
2006-03-21 3:25 ` Balbir Singh
2006-03-21 10:51 ` Bodo Eggert
2006-03-21 11:32 ` Pekka J 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=1142871263.11694.4.camel@localhost \
--to=penberg@cs.helsinki.fi \
--cc=akpm@osdl.org \
--cc=balbir@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.