From: "Bob Picco" <bob.picco@hp.com>
To: Andi Kleen <ak@suse.de>
Cc: Yasunori Goto <y-goto@jp.fujitsu.com>,
Christoph Lameter <clameter@engr.sgi.com>,
torvalds@osdl.org, akpm@osdl.org, linux-mm@kvack.org
Subject: Re: [PATCH for 2.6.16] Handle holes in node mask in node fallback list initialization
Date: Fri, 17 Feb 2006 06:23:24 -0500 [thread overview]
Message-ID: <20060217112324.GA31068@localhost> (raw)
In-Reply-To: <200602171058.33078.ak@suse.de>
Andi Kleen wrote: [Fri Feb 17 2006, 04:58:32AM EST]
> On Friday 17 February 2006 07:10, Yasunori Goto wrote:
> > > > Empty nodes are not initialization, but the node number is still
> > > > allocated. And then it would early except or even triple fault here
> > > > because it would try to set up a fallback list for a NULL pgdat. Oops.
> > >
> > > Isnt this an issue with the arch code? Simply do not allocate an empty
> > > node. Is the mapping from linux Node id -> Hardware node id fixed on
> > > x86_64? ia64 has a lookup table.
> >
> > Do you mention about pxm_to_nid_map[]?
>
> I think he refers to cpu_to_node[]
>
> > Ia64 added the feature of memory less node long time ago.
>
> x86-64 too, but it just bitrotted and that is what I was trying to fix.
> I did some tests with a simulator in a few combinations of memory less
> CPUs and with the two patches they all boot so far. But will test it out more.
>
> -Andi
>
> --
Yasunori thanks for mentioning memory less nodes for ia64. This is my
concern with the patch. I need to test/review the patch on HP
hardware/simulator (most default configured HP NUMA machines are memory less -
interleaved memory). This has caused us numerous NUMA issues.
bob
--
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>
next prev parent reply other threads:[~2006-02-17 11:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 1:23 Andi Kleen
2006-02-17 1:40 ` Christoph Lameter
2006-02-17 1:46 ` Andi Kleen
2006-02-17 2:12 ` KAMEZAWA Hiroyuki
2006-02-17 1:51 ` Christoph Lameter
2006-02-17 2:10 ` Andi Kleen
2006-02-17 2:46 ` Christoph Lameter
2006-02-17 6:10 ` Yasunori Goto
2006-02-17 9:58 ` Andi Kleen
2006-02-17 11:23 ` Bob Picco [this message]
2006-02-17 12:15 ` Andi Kleen
2006-02-17 14:34 ` Lee Schermerhorn
2006-02-17 16:05 ` Christoph Lameter
2006-02-17 3:33 ` Yasunori Goto
2006-02-17 16:52 ` Linus Torvalds
2006-02-17 18:07 ` Andi Kleen
2006-02-17 18:38 ` Linus Torvalds
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=20060217112324.GA31068@localhost \
--to=bob.picco@hp.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=clameter@engr.sgi.com \
--cc=linux-mm@kvack.org \
--cc=torvalds@osdl.org \
--cc=y-goto@jp.fujitsu.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