From: Andi Kleen <ak@suse.de>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, y-goto@jp.fujitsu.com,
clameter@engr.sgi.com, akpm@osdl.org
Subject: Re: [2.6.20][PATCH] fix mempolicy error check on a system with memory-less-node
Date: Wed, 7 Feb 2007 11:19:02 +0100 [thread overview]
Message-ID: <200702071119.03125.ak@suse.de> (raw)
In-Reply-To: <20070207190738.30f1d419.kamezawa.hiroyu@jp.fujitsu.com>
> AFAIK, ia64 creates nodes just depends on SRAT's possible resource information.
> Then, ia64 can create cpu-memory-less-node(node with no available resource.).
> (*)I don't like this.
>
> If we don't allow memory-less-node, we may have to add several codes for cpu-hot-add.
> cpus should be moved to nearby node at hotadd .
> And node-hot-add have to care that cpus mustn't be added before memory, cpu-driven
> node-hot-add will never occur. (ACPI's 'container' device spec can't guaranntee this.)
You can also alias node numbers to solve this: just point multiple node numbers
to the same pgdat. For a memory less node this would be a nearby one.
-Andi
next prev parent reply other threads:[~2007-02-07 10:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 11:23 [2.6.20][PATCH] fix mempolicy error check on a system with memory-less-node KAMEZAWA Hiroyuki
2007-02-06 17:26 ` Christoph Lameter
2007-02-07 1:14 ` KAMEZAWA Hiroyuki
2007-02-07 8:04 ` Christoph Lameter
2007-02-07 8:36 ` KAMEZAWA Hiroyuki
2007-02-08 11:49 ` Bob Picco
2007-02-07 10:20 ` Andi Kleen
2007-02-07 10:20 ` Andi Kleen
2007-02-07 10:07 ` KAMEZAWA Hiroyuki
2007-02-07 10:19 ` Andi Kleen [this message]
2007-02-07 10:37 ` KAMEZAWA Hiroyuki
2007-02-07 10:41 ` Andi Kleen
2007-02-07 10:49 ` KAMEZAWA Hiroyuki
2007-02-07 11:32 ` Andi Kleen
2007-02-07 12:27 ` KAMEZAWA Hiroyuki
2007-02-07 14:05 ` Christoph Lameter
2007-02-07 15:28 ` KAMEZAWA Hiroyuki
2007-02-07 14:03 ` Christoph Lameter
2007-02-07 16:23 ` Andrew Morton
2007-02-07 16:50 ` Andi Kleen
2007-02-07 17:43 ` Andrew Morton
2007-02-07 18:15 ` [PATCH] FS : Speedup rw_verify_area() Eric Dumazet
2007-02-08 0:37 ` [2.6.20][PATCH] fix mempolicy error check on a system with memory-less-node KAMEZAWA Hiroyuki
2007-02-08 19:09 ` Christoph Lameter
2007-02-08 19:26 ` Andrew Morton
2007-02-08 19:35 ` Christoph Lameter
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=200702071119.03125.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=clameter@engr.sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.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