From: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
To: David Rientjes <rientjes@google.com>
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
benh@kernel.crashing.org,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
nfont@linux.vnet.ibm.com,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Cody P Schafer <cody@linux.vnet.ibm.com>,
Anton Blanchard <anton@samba.org>, Dave Hansen <dave@sr71.net>,
"linuxppc-dev@lists.ozlabs.org list"
<linuxppc-dev@lists.ozlabs.org>, Linux MM <linux-mm@kvack.org>
Subject: Re: NUMA topology question wrt. d4edc5b6
Date: Tue, 10 Jun 2014 16:30:59 -0700 [thread overview]
Message-ID: <20140610233059.GA24463@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1406091436090.5271@chino.kir.corp.google.com>
On 09.06.2014 [14:38:26 -0700], David Rientjes wrote:
> On Fri, 23 May 2014, Srivatsa S. Bhat wrote:
>
> > diff --git a/arch/powerpc/include/asm/topology.h b/arch/powerpc/include/asm/topology.h
> > index c920215..58e6469 100644
> > --- a/arch/powerpc/include/asm/topology.h
> > +++ b/arch/powerpc/include/asm/topology.h
> > @@ -18,6 +18,7 @@ struct device_node;
> > */
> > #define RECLAIM_DISTANCE 10
> >
> > +#include <linux/nodemask.h>
> > #include <asm/mmzone.h>
> >
> > static inline int cpu_to_node(int cpu)
> > @@ -30,7 +31,7 @@ static inline int cpu_to_node(int cpu)
> > * During early boot, the numa-cpu lookup table might not have been
> > * setup for all CPUs yet. In such cases, default to node 0.
> > */
> > - return (nid < 0) ? 0 : nid;
> > + return (nid < 0) ? first_online_node : nid;
> > }
> >
> > #define parent_node(node) (node)
>
> I wonder what would happen on ppc if we just returned NUMA_NO_NODE here
> for cpus that have not been mapped (they shouldn't even be possible).
Well, with my patch (Ben sent it to Linus in the last pull request, I
think), powerpc uses the generic per-cpu stuff, so this function is
gone. Dunno if it makes sense to initialize the per-cpu data to
NUMA_NO_NODE (rather than 0?).
For powerpc, it's a timing thing. We can call cpu_to_node() quite early,
and we may not have set up the mapping information yet.
> This would at least allow callers that do
> kmalloc_node(..., cpu_to_node(cpu)) to be allocated on the local cpu
> rather than on a perhaps offline or remote node 0.
>
> It would seem better to catch callers that do
> cpu_to_node(<not-possible-cpu>) rather than blindly return an online node.
Agreed, but I've not seen such a case.
Thanks,
Nish
--
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:[~2014-06-10 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140521200451.GB5755@linux.vnet.ibm.com>
2014-05-22 20:48 ` NUMA topology question wrt. d4edc5b6 Srivatsa S. Bhat
2014-05-28 20:37 ` Nishanth Aravamudan
2014-06-09 21:38 ` David Rientjes
2014-06-10 23:30 ` Nishanth Aravamudan [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=20140610233059.GA24463@linux.vnet.ibm.com \
--to=nacc@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=cody@linux.vnet.ibm.com \
--cc=dave@sr71.net \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nfont@linux.vnet.ibm.com \
--cc=rientjes@google.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=srivatsa.bhat@linux.vnet.ibm.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).