From: Matthew Dobson <colpatch@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Lse-tech] fix zonelist ordering for NUMA
Date: Tue, 24 Feb 2004 19:49:56 +0000 [thread overview]
Message-ID: <1077652196.26287.6.camel@arrakis> (raw)
On Tue, 2004-02-24 at 01:20, j-nomura@ce.jp.nec.com wrote:
> - for (node = local_node + 1; node < numnodes; node++)
> - j = build_zonelists_node(NODE_DATA(node), zonelist, j, k);
> - for (node = 0; node < local_node; node++)
> - j = build_zonelists_node(NODE_DATA(node), zonelist, j, k);
> + for (node = 1; node < numnodes; node++)
> + j = build_zonelists_node(SORTED_NODE_DATA(local_node, node), zonelist, j, k);
Shouldn't that for loop be:
for (node = 0; node < numnodes; node++)
j = ....
or we'll be leaving a node out of the zonelists, right?
-Matt
next reply other threads:[~2004-02-24 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 19:49 Matthew Dobson [this message]
2004-02-25 5:02 ` [Lse-tech] fix zonelist ordering for NUMA j-nomura
2004-02-25 10:59 ` j-nomura
2004-02-25 11:28 ` Christoph Hellwig
2004-02-25 16:52 ` Jesse Barnes
2004-02-27 5:31 ` j-nomura
2004-02-27 12:19 ` j-nomura
2004-02-27 17:33 ` Jesse Barnes
2004-03-01 14:08 ` 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=1077652196.26287.6.camel@arrakis \
--to=colpatch@us.ibm.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