From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Christoph Lameter <christoph@lameter.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, manfred@colorfullife.com
Subject: Re: [PATCH] slab: minor cleanup to kmem_cache_alloc_node
Date: Mon, 21 Nov 2005 20:36:34 +0200 [thread overview]
Message-ID: <1132598194.8972.4.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.62.0511210919001.6497@graphe.net>
On Mon, 2005-11-21 at 09:21 -0800, Christoph Lameter wrote:
> On Mon, 21 Nov 2005, Pekka J Enberg wrote:
>
> > This patch gets rid of one if-else statement by moving current node allocation
> > check at the beginning of kmem_cache_alloc_node().
>
> The problem with this is that the numa_node may change if irqs are still
> active and your patch moves the check for the numa node outside of the
> section where irqs are enabled.
>
> You could move the check for -1 into the section where interrupts are
> disabled.
So we could do something like the following. Unfortunately it does not
seem much of an improvement... Thoughts?
Pekka
Index: 2.6/mm/slab.c
===================================================================
--- 2.6.orig/mm/slab.c
+++ 2.6/mm/slab.c
@@ -2866,21 +2866,23 @@ void *kmem_cache_alloc_node(kmem_cache_t
unsigned long save_flags;
void *ptr;
- if (nodeid == -1)
- return __cache_alloc(cachep, flags);
+ cache_alloc_debugcheck_before(cachep, flags);
+ local_irq_save(save_flags);
+
+ if (nodeid == -1 || nodeid == numa_node_id()) {
+ ptr = ____cache_alloc(cachep, flags);
+ goto out;
+ }
if (unlikely(!cachep->nodelists[nodeid])) {
/* Fall back to __cache_alloc if we run into trouble */
printk(KERN_WARNING "slab: not allocating in inactive node %d for cache %s\n", nodeid, cachep->name);
- return __cache_alloc(cachep,flags);
+ ptr = ____cache_alloc(cachep,flags);
+ goto out;
}
- cache_alloc_debugcheck_before(cachep, flags);
- local_irq_save(save_flags);
- if (nodeid == numa_node_id())
- ptr = ____cache_alloc(cachep, flags);
- else
- ptr = __cache_alloc_node(cachep, flags, nodeid);
+ ptr = __cache_alloc_node(cachep, flags, nodeid);
+ out:
local_irq_restore(save_flags);
ptr = cache_alloc_debugcheck_after(cachep, flags, ptr, __builtin_return_address(0));
next prev parent reply other threads:[~2005-11-21 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 14:30 [PATCH] slab: minor cleanup to kmem_cache_alloc_node Pekka J Enberg
2005-11-21 15:58 ` Eric Dumazet
2005-11-21 16:23 ` Pekka Enberg
2005-11-21 17:21 ` Christoph Lameter
2005-11-21 18:36 ` Pekka Enberg [this message]
2005-11-21 19:47 ` Christoph Lameter
2005-11-21 21:07 ` Pekka Enberg
2005-11-21 21:17 ` Christoph Lameter
2005-11-22 6:57 ` 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=1132598194.8972.4.camel@localhost \
--to=penberg@cs.helsinki.fi \
--cc=akpm@osdl.org \
--cc=christoph@lameter.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox