From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slab: introduce kmem_cache_zalloc allocator
Date: Tue, 21 Mar 2006 20:37:21 +0200 [thread overview]
Message-ID: <1142966242.23941.0.camel@localhost> (raw)
In-Reply-To: <44204754.8070401@colorfullife.com>
On Tue, 2006-03-21 at 19:35 +0100, Manfred Spraul wrote:
> One minor point: There are two cache_alloc entry points: __cache_alloc,
> which is a forced inline function, and kmem_cache_alloc, which is just a
> wrapper for __cache_alloc. Is it really necessary to call __cache_alloc?
Unfortunately, yes. Using kmem_cache_alloc screws up caller tracing.
Pekka
next prev parent reply other threads:[~2006-03-21 18:37 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
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 [this message]
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=1142966242.23941.0.camel@localhost \
--to=penberg@cs.helsinki.fi \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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.