From: Yasunori Goto <ygoto@us.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Lhns-devel] Re: Who's doing what with cpu/memory/node hotplug?
Date: Fri, 14 May 2004 00:13:15 +0000 [thread overview]
Message-ID: <20040513150842.22F5.YGOTO@us.fujitsu.com> (raw)
Hello.
> > Iam not sure what specifically you are looking for ...
>
> I was looking for the short and sweet overview such as you just
> presented ;). Thanks.
>
> I need to start following this hotplug work because it is next door to
> the cpu/memory placement work that I am most focused on, such as
> cpusets, led by Simon Derr of Bull, sitting on top of sched_setaffinity
> and Andi Kleen's numa work. A cpuset is a set of cpu and memory
> resources that several tasks share, perhaps exclusively (all other
> tasks kept out).
>
> 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.
But did you see Iwamoto-san's patch ?
This is infrastructure that contents of memory can
migrate from a node to other node.
If remap_onepage() of his patch execute on same cpus of that process
or 'node id' is specified, it will migrate to appriciate node.
I think it can be your help.
But, probably you might think many other works are necessary, right?
Thanks.
--
Yasunori Goto <ygoto at us.fujitsu.com>
-------------------------------------------------------
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 reply other threads:[~2004-05-14 0:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 0:13 Yasunori Goto [this message]
2004-05-14 1:06 ` [Lhns-devel] Re: Who's doing what with cpu/memory/node hotplug? 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
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=20040513150842.22F5.YGOTO@us.fujitsu.com \
--to=ygoto@us.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;
as well as URLs for NNTP newsgroup(s).