From: Dave Hansen <haveblue@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 05:31:56 +0000 [thread overview]
Message-ID: <1084771915.24128.4931.camel@nighthawk> (raw)
In-Reply-To: <20040513150842.22F5.YGOTO@us.fujitsu.com>
On Thu, 2004-05-13 at 17:13, Yasunori Goto wrote:
> > At some point, questions such as "what happens when a node is unplugged
> > from a cpuset" will need to be answered. And even earlier, "what happens
> > when a cpu is unplugged that was in a tasks cpus_allowed, or a memory
> > node unplugged, that was in a vma's list of allowed memory zones."
> >
> > Or perhaps the answers to these questions are already known ??
>
> At least, there aren't enough answer about memory hotplug yet
> if there is a process that is using memory affinity.
There's been a lot of talk of what to do with hotplug CPUs as well. No
matter what, it's going to be really easy to notify whatever app you
want with the hotplug scripts whenever a memory or CPU event happens.
Just place your app script in /etc/hotplug.d.
-- 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-17 5:31 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 [this message]
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
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=1084771915.24128.4931.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).