From: Christoph Lameter <clameter@sgi.com>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: manfred@colorfullife.com, christoph@lameter.com, pj@sgi.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC/PATCH] slab: clean up allocation
Date: Fri, 29 Sep 2006 09:10:55 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0609290906350.23840@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0609291353060.30021@sbz-30.cs.Helsinki.FI>
On Fri, 29 Sep 2006, Pekka J Enberg wrote:
> + * When allocating from current node.
> + */
> +#define SLAB_CURRENT_NODE (-1)
> +
If we want a constant here then we would better define a global one and
use it throughout the kernel.
Something like
#define LOCAL_NODE (-1)
Maybe in include/*/topology.h ?
> #endif
>
> -static inline void *____cache_alloc(struct kmem_cache *cachep, gfp_t flags)
> +static inline void *cache_alloc_local(struct kmem_cache *cachep, gfp_t flags)
> {
> void *objp;
> struct array_cache *ac;
> @@ -3059,35 +3064,6 @@ static inline void *____cache_alloc(stru
> return objp;
> }
This is not really local in the sense of node local but its processor
local. The speciality here is that we allocate from the per processor
list of objects. cache_alloc_cpu?
The rest looks fine on first glance.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2006-09-29 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 10:56 Pekka J Enberg
2006-09-29 16:10 ` Christoph Lameter [this message]
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=Pine.LNX.4.64.0609290906350.23840@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=christoph@lameter.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.com \
--cc=penberg@cs.helsinki.fi \
--cc=pj@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox