From: Tejun Heo <tj@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: H Hartley Sweeten <hartleys@visionengravers.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
x86@kernel.org, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, penberg@kernel.org, yinghai@kernel.org
Subject: Re: [PATCH] arch/x86/mm/numa.c: quiet sparse noise when CONFIG_X86_64 is not set
Date: Sun, 11 Sep 2011 10:06:19 +0900 [thread overview]
Message-ID: <20110911010619.GG29319@htj.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1109100238110.17756@chino.kir.corp.google.com>
Hello,
On Sat, Sep 10, 2011 at 02:39:02AM -0700, David Rientjes wrote:
> On Fri, 9 Sep 2011, H Hartley Sweeten wrote:
>
> > diff --git a/arch/x86/mm/numa.c b/arch/x86/mm/numa.c
> > index fbeaaf4..11c60a7 100644
> > --- a/arch/x86/mm/numa.c
> > +++ b/arch/x86/mm/numa.c
> > @@ -455,6 +455,7 @@ void __init numa_set_distance(int from, int to, int distance)
> > numa_distance[from * numa_distance_cnt + to] = distance;
> > }
> >
> > +#ifdef CONFIG_X86_64
> > int __node_distance(int from, int to)
> > {
> > if (from >= numa_distance_cnt || to >= numa_distance_cnt)
> > @@ -462,6 +463,7 @@ int __node_distance(int from, int to)
> > return numa_distance[from * numa_distance_cnt + to];
> > }
> > EXPORT_SYMBOL(__node_distance);
> > +#endif
> >
> > /*
> > * Sanity check to catch more bad NUMA configurations (they are amazingly
> >
>
> What is 64-bit specific about this function? Shouldn't we be defining it
> to be node_distance for all of x86?
Yeap, that's a remnant of the old separate code paths, which wasn't
discovered because asm-generic/topology.h defines fallback
node_distance() automatically. We should drop #ifdef from
arch/x86/include/asm/topology.h::node_distance(). Hartley, can you
please send a patch to do that?
Thanks.
--
tejun
next prev parent reply other threads:[~2011-09-11 1:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 23:38 H Hartley Sweeten
2011-09-10 9:39 ` David Rientjes
2011-09-11 1:06 ` Tejun Heo [this message]
2011-09-19 23:05 ` H Hartley Sweeten
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=20110911010619.GG29319@htj.dyndns.org \
--to=tj@kernel.org \
--cc=hartleys@visionengravers.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.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
all inboxes | Powered by JetHome®