From: Dave Hansen <haveblue@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Who's doing what with cpu/memory/node hotplug?
Date: Thu, 13 May 2004 06:50:58 +0000 [thread overview]
Message-ID: <1084431058.3189.7.camel@nighthawk> (raw)
In-Reply-To: <20040512205107.16bb82a6.pj@sgi.com>
On Wed, 2004-05-12 at 23:35, Keiichiro Tokunaga wrote:
> > Node Hotplug support - Tokunaga-san (fujitsu) mostly concentrating on
> > ACPI based numa node hotplug. This work is independent
> > of rest of the hotplug (atleast mostly) and would invoke other module
> > hotplug code as required. (roughly @10000 ft level)
>
> I'm rather focusing on ACPI based container device hotplug.
> A scope of LHNS includes a container device that contains
> IO devices. I think such a devices couldn't be handled by NUMA
> hotplug.
Why not? We already export the information about which PCI busses are
attached to which NUMA nodes. How are I/O devices different from CPU or
memory?
BTW, what *is* NUMA hotplug? :)
-- Dave
-------------------------------------------------------
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-13 6:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 3:51 Who's doing what with cpu/memory/node hotplug? Paul Jackson
2004-05-13 4:23 ` Dave Hansen
2004-05-13 4:44 ` Ashok Raj
2004-05-13 4:59 ` Paul Jackson
2004-05-13 6:35 ` Keiichiro Tokunaga
2004-05-13 6:50 ` Dave Hansen [this message]
2004-05-13 7:18 ` Paul Jackson
2004-05-13 14:00 ` Jack Steiner
2004-05-13 16:01 ` Dave Hansen
2004-05-13 16:33 ` Jack Steiner
2004-05-14 1:14 ` Keiichiro Tokunaga
2004-05-14 13:49 ` Russ Anderson
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=1084431058.3189.7.camel@nighthawk \
--to=haveblue@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).