From: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Lee Schermerhorn <lee.schermerhorn@hp.com>,
Christoph Lameter <cl@linux-foundation.org>,
Mel Gorman <mel@csn.ul.ie>,
linux-mm@kvack.org, Anton Blanchard <anton@samba.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH v2 1/2] powerpc: numa: enable USE_PERCPU_NUMA_NODE_ID
Date: Tue, 27 May 2014 16:44:20 -0700 [thread overview]
Message-ID: <20140527234420.GE4104@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140519181423.GL8941@linux.vnet.ibm.com>
On 19.05.2014 [11:14:23 -0700], Nishanth Aravamudan wrote:
> Hi Andrew,
>
> I found one issue with my patch, fixed below...
>
> On 16.05.2014 [16:39:45 -0700], Nishanth Aravamudan wrote:
> > Based off 3bccd996 for ia64, convert powerpc to use the generic per-CPU
> > topology tracking, specifically:
> >
> > initialize per cpu numa_node entry in start_secondary
> > remove the powerpc cpu_to_node()
> > define CONFIG_USE_PERCPU_NUMA_NODE_ID if NUMA
> >
> > Signed-off-by: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
>
> <snip>
>
> > diff --git a/arch/powerpc/kernel/smp.c b/arch/powerpc/kernel/smp.c
> > index e2a4232..b95be24 100644
> > --- a/arch/powerpc/kernel/smp.c
> > +++ b/arch/powerpc/kernel/smp.c
> > @@ -750,6 +750,11 @@ void start_secondary(void *unused)
> > }
> > traverse_core_siblings(cpu, true);
> >
> > + /*
> > + * numa_node_id() works after this.
> > + */
> > + set_numa_node(numa_cpu_lookup_table[cpu]);
> > +
>
> Similar change is needed for the boot CPU. Update patch:
>
>
> powerpc: numa: enable USE_PERCPU_NUMA_NODE_ID
>
> Based off 3bccd996 for ia64, convert powerpc to use the generic per-CPU
> topology tracking, specifically:
>
> initialize per cpu numa_node entry in start_secondary
> remove the powerpc cpu_to_node()
> define CONFIG_USE_PERCPU_NUMA_NODE_ID if NUMA
>
> Signed-off-by: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
Ping on this and patch 2/2. Ben, would you be willing to pull these into
your -next branch so they'd get some testing?
http://patchwork.ozlabs.org/patch/350368/
http://patchwork.ozlabs.org/patch/349838/
Without any further changes, these two help quite a bit with the slab
consumption on CONFIG_SLUB kernels when memoryless nodes are present.
Thanks,
Nish
next prev parent reply other threads:[~2014-05-27 23:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 23:39 [PATCH] powerpc: numa: enable USE_PERCPU_NUMA_NODE_ID Nishanth Aravamudan
2014-05-16 23:41 ` [PATCH 2/2] powerpc: numa: enable CONFIG_HAVE_MEMORYLESS_NODES Nishanth Aravamudan
2014-05-19 18:14 ` [RFC PATCH v2 1/2] powerpc: numa: enable USE_PERCPU_NUMA_NODE_ID Nishanth Aravamudan
2014-05-27 23:44 ` Nishanth Aravamudan [this message]
2014-05-27 23:56 ` Benjamin Herrenschmidt
2014-05-28 0:09 ` Nishanth Aravamudan
2014-05-28 23:36 ` Andrew Morton
2014-05-28 23:43 ` Nishanth Aravamudan
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=20140527234420.GE4104@linux.vnet.ibm.com \
--to=nacc@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=cl@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mel@csn.ul.ie \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).