From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kosaki.motohiro@jp.fujitsu.com,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH] cpumask: alloc_cpumask_var() use NUMA_NO_NODE
Date: Mon, 9 May 2011 09:29:06 +0900 (JST) [thread overview]
Message-ID: <20110509093043.3ABB.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20110505124556.3c8a7e5b.akpm@linux-foundation.org>
Hi
> On Thu, 28 Apr 2011 23:17:15 +0900 (JST)
> KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
>
> > NUMA_NO_NODE and numa_node_id() are different meanings. NUMA_NO_NODE
> > is obviously recomended fallback.
> >
> > Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> > ---
> > lib/cpumask.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/lib/cpumask.c b/lib/cpumask.c
> > index 4f6425d..af3e581 100644
> > --- a/lib/cpumask.c
> > +++ b/lib/cpumask.c
> > @@ -131,7 +131,7 @@ EXPORT_SYMBOL(zalloc_cpumask_var_node);
> > */
> > bool alloc_cpumask_var(cpumask_var_t *mask, gfp_t flags)
> > {
> > - return alloc_cpumask_var_node(mask, flags, numa_node_id());
> > + return alloc_cpumask_var_node(mask, flags, NUMA_NO_NODE);
> > }
> > EXPORT_SYMBOL(alloc_cpumask_var);
> >
>
> So effectively this will replace numa_node_id() with numa_mem_id(),
> yes? What runtime effects might this have?
If I understand correctly,
alloc_pages_node(): same effect both NUMA_NO_NODE and numa_node_id()
kmalloc_node(): not same effect NUMA_NO_NODE and numa_node_id()
because
slub.c
---------------------------------------------------
slab_alloc() {
(snip)
if (unlikely(!object || !node_match(c, node)))
// slow path
else {
// fast path
and
static inline int node_match(struct kmem_cache_cpu *c, int node)
{
#ifdef CONFIG_NUMA
if (node != NUMA_NO_NODE && c->node != node)
return 0;
#endif
return 1;
}
---------------------------------------------------
In a nutshell, numa_node_id() reduce slab cache reusing chance.
Oh, I missed slab.c code. It's using numa_mem_id(). thank you correct me!
numa_mem_id() don't have much meanings. It's ia64 HP big machine quirk.
it only affect to improve slab performance a little if users try to allocate
a memory from a cpu within memoryless node . and, 99% users never use such machine.
In a nutshell, NUMA_NO_NODE and numa_node_id() don't have a lot of difference
if users are using SLAB.
prev parent reply other threads:[~2011-05-09 0:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 14:17 KOSAKI Motohiro
2011-05-05 19:45 ` Andrew Morton
2011-05-09 0:29 ` KOSAKI Motohiro [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=20110509093043.3ABB.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome