public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keiichiro Tokunaga <tokunaga.keiich@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Who's doing what with cpu/memory/node hotplug?
Date: Fri, 14 May 2004 01:14:04 +0000	[thread overview]
Message-ID: <20040514101404.6bedda69.tokunaga.keiich@jp.fujitsu.com> (raw)
In-Reply-To: <20040512205107.16bb82a6.pj@sgi.com>

On Wed, 12 May 2004 23:50:58 -0700
Dave Hansen <haveblue@us.ibm.com> wrote:

> 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?  

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?

> BTW, what *is* NUMA hotplug? :)

I'm sorry, that would have to be "NUMA node hotplug"...

Thanks,
Kei

  parent reply	other threads:[~2004-05-14  1:14 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
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 [this message]
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=20040514101404.6bedda69.tokunaga.keiich@jp.fujitsu.com \
    --to=tokunaga.keiich@jp.fujitsu.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