From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Lse-tech] Re: fix zonelist ordering for NUMA
Date: Thu, 26 Feb 2004 22:21:02 +0000 [thread overview]
Message-ID: <100070000.1077834062@flay> (raw)
--On Wednesday, February 25, 2004 08:54:09 -0800 Jesse Barnes <jbarnes@sgi.com> wrote:
> On Wed, Feb 25, 2004 at 02:01:16PM +0900, j-nomura@ce.jp.nec.com wrote:
>> > 1) make it arch independent
>> > this means having arch code populate a SLIT-like table for use by
>> > the generic zonelist building code
>>
>> I would like to hear the comments from people on other arch.
>> If the same ordering rule can be applicable for others, it's nice.
>
> Martin, does a scheme like this sound ok with you? Arch specific code
> would populate a node distance table, which would be used to build each
> pgdat->zonelist in a smarter way than we do currently.
Yeah, looks sensible to me. We probably ought to do this:
+#ifndef node_distance
+#define node_distance(from,to) (1)
+#endif
in the generic fallback topology headers, not in the mm/ .c files. Matt?
Also, I seem to recall those build_zonelists functions are used for both
NUMA and UMA ... now they're getting complex enough that it's probably
worth making a specific non-NUMA version, if only for the sanity of
99% of the poor souls trying to work out how a UMA machine lays it out ;-)
It looks like it won't change ordering for existing boxes with single
layer flat NUMA topologies (round-robin), but we probably ought to check
that carefully ;-)
M.
next reply other threads:[~2004-02-26 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 22:21 Martin J. Bligh [this message]
2004-02-26 23:09 ` [Lse-tech] Re: fix zonelist ordering for NUMA Matthew Dobson
2004-02-26 23:40 ` Dave Hansen
2004-02-26 23:54 ` Martin J. Bligh
2004-02-27 0:47 ` Chris Wedgwood
2004-02-27 0:56 ` Martin J. Bligh
2004-02-27 5:38 ` j-nomura
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=100070000.1077834062@flay \
--to=mbligh@aracnet.com \
--cc=linux-ia64@vger.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