From: Matthew Dobson <colpatch@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Lhns-devel] Re: Who's doing what with cpu/memory/node hotplug?
Date: Mon, 17 May 2004 23:01:21 +0000 [thread overview]
Message-ID: <1084834881.4095.20.camel@arrakis> (raw)
In-Reply-To: <20040513150842.22F5.YGOTO@us.fujitsu.com>
On Sun, 2004-05-16 at 19:34, Kenji Kaneshige wrote:
> Hi,
>
> > > I have just one concern.
> > > How about a container device that contains IO devices only?
> > > - Does it count as a NUMA node?
> > > - Is it having a NUMA node ID?
> >
> > Yes, it would count as NUMA node with a NUMA ID.
> >
> > So a NUMA node could have CPUs, memory, and I/O,
> > where each of those may or may not be present.
> >
> > There could be a node without any CPU, memory, or I/O.
> > An example would be an I/O only node with PCI devices
> > that are hot plug. The PCI devices may or may not be
> > connected at any point in time.
>
> I don't know about NUMA much, but I think NUMA node ID is based
> on the SRAT at the boot time. But SRAT doesn't have entries for I/O
> devices. How should we create the NUMA node ID for I/O nodes at the
> boot time?
>
> Thanks,
> Kenji Kaneshige
The NUMA node ID *can* be based on the SRAT, but doesn't *have* to be.
It's really up to each individual architecture how they want to number
their nodes. Or at least that's the way things should work. That was a
large part of the motivation behind the nodemask patches I submitted a
while ago. We would like individual architectures to be able to number
their nodes in any manner they deem appropriate, as long as 0 <= nid <
MAX_NUMNODES. Currently there is an additional requirement (that the
nodemask code would eliminate) that nodes must be numbered sequentially
without any gaps in the numbering, ie: 0 <= nid < numnodes. There is
really no good reason that this has to hold, so we should get rid of it.
We want macros like for_each_node_with_cpus(),
for_each_node_with_memory(), etc, that people can use to iterate over
the type of nodes they care about.
I'd look at SGI's IA64 code for examples of how to create NUMA nodes
with only I/O on them.
-Matt
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id%62&alloc_ida84&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-05-17 23:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 0:13 [Lhns-devel] Re: Who's doing what with cpu/memory/node hotplug? Yasunori Goto
2004-05-14 1:06 ` Paul Jackson
2004-05-14 1:28 ` Dave Hansen
2004-05-14 2:09 ` Jesse Barnes
2004-05-14 3:02 ` Keiichiro Tokunaga
2004-05-14 3:21 ` Dave Hansen
2004-05-17 2:34 ` Kenji Kaneshige
2004-05-17 5:31 ` Dave Hansen
2004-05-17 7:35 ` Matthias Fouquet-Lapar
2004-05-17 8:23 ` Dave Hansen
2004-05-17 8:38 ` Matthias Fouquet-Lapar
2004-05-17 15:45 ` Grant Grundler
2004-05-17 15:52 ` Dave Hansen
2004-05-17 16:00 ` Ashok Raj
2004-05-17 19:15 ` Matthias Fouquet-Lapar
2004-05-17 23:01 ` Matthew Dobson [this message]
2004-05-17 23:18 ` Luck, Tony
2004-05-17 23:28 ` Dave Hansen
2004-05-17 23:36 ` Jesse Barnes
2004-05-17 23:54 ` Grant Grundler
2004-05-18 14:58 ` Russ Anderson
2004-05-18 20:16 ` Ashok Raj
2004-05-18 21:01 ` Jack Steiner
2004-05-18 21:05 ` Andi Kleen
2004-05-18 21:12 ` Greg KH
2004-05-19 5:25 ` Matthias Fouquet-Lapar
2004-05-19 9:17 ` Paul Jackson
2004-05-19 9:30 ` Matthias Fouquet-Lapar
2004-05-19 10:22 ` Paul Jackson
2004-05-19 14:40 ` Howell, David P
2004-05-19 14:56 ` Matthias Fouquet-Lapar
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=1084834881.4095.20.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;
as well as URLs for NNTP newsgroup(s).