From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Andi Kleen <ak@suse.de>,
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 15:10:04 +0900 [thread overview]
Message-ID: <20060217145409.4064.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0602161749330.27091@schroedinger.engr.sgi.com>
> > 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 picked it out to driver/acpi/numa.c. (see: current -mm)
It is not arch specific. pxm is acpi's spec, and node id is generic
linux kernel code. :-P
> These are empty nodes without processor? Or a processor without a node?
> In that case the processor will have to be assigned a default node.
???
Ia64 added the feature of memory less node long time ago.
This is in arch/ia64/mm/discontig.c
406 /**
407 * memory_less_nodes - allocate and initialize CPU only nodes pernode
408 * information.
410 static void __init memory_less_nodes(void)
411 {
409 */
:
:
Bye.
--
Yasunori Goto
--
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 6:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 1:23 [PATCH for 2.6.16] Handle holes in node mask in node fallback list initialization 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 [this message]
2006-02-17 9:58 ` Andi Kleen
2006-02-17 11:23 ` Bob Picco
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=20060217145409.4064.Y-GOTO@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=clameter@engr.sgi.com \
--cc=linux-mm@kvack.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.