From: Jack Steiner <steiner@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC][PATCH] avoid creating empty nodes [0/2]
Date: Wed, 29 Mar 2006 14:37:34 +0000 [thread overview]
Message-ID: <20060329143733.GA15473@sgi.com> (raw)
In-Reply-To: <20060329110903.d7bae796.kamezawa.hiroyu@jp.fujitsu.com>
On Wed, Mar 29, 2006 at 11:09:03AM +0900, KAMEZAWA Hiroyuki wrote:
> When I tesetd new firmware , which supports NUMA cpu/memory hot-add
> (with Windows), I found Linux/ia64 creates nodes with no cpus, no memory.
I don't see any problems with your patch in the short term. However, long
term, we may need to make changes & support nodes with no memory or cpus.
An SGI Altix SSI system consists of a collection of nodes connected via a
high speed interconnect. Nodes come in several flavors:
- memory, IO and cpus
- memory & cpus
- memory only
- IO only
You can think of the last 3 types of nodes as nodes that have been partially
depopulated. This isn't entirely accurate but is good enough to gain an
understanding of the problem.
Currently, IO nodes are not defined in the SRAT tables because there is no
way to describe them. Most of the kernel is unaware of IO nodes. There are
hacks in the SN code that have extended the definition of nodes (cnodes) to
include IO nodes. However, this is just an interim solution & we intend to
fix it.
ACPI3.0 will have a way to describe these IO nodes. We have not done the
design but when ACPI3.0 is available, we intend to make the kernel fully
aware of IO-only nodes.
next prev parent reply other threads:[~2006-03-29 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 2:09 [RFC][PATCH] avoid creating empty nodes [0/2] KAMEZAWA Hiroyuki
2006-03-29 2:11 ` [RFC][PATCH] avoid creating empty nodes [1/2] move reserve memory KAMEZAWA Hiroyuki
2006-03-29 2:12 ` [RFC][PATCH] avoid creating empty nodes [2/2] ignore empty pxms KAMEZAWA Hiroyuki
2006-03-29 14:37 ` Jack Steiner [this message]
2006-03-29 23:31 ` [RFC][PATCH] avoid creating empty nodes [0/2] KAMEZAWA Hiroyuki
2006-03-30 1:38 ` Jack Steiner
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=20060329143733.GA15473@sgi.com \
--to=steiner@sgi.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