From: Paul Jackson <pj@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Who's doing what with cpu/memory/node hotplug?
Date: Thu, 13 May 2004 03:51:07 +0000 [thread overview]
Message-ID: <20040512205107.16bb82a6.pj@sgi.com> (raw)
Could someone explain to me who's doing what with cpu, memory and node hotplug?
In particular, I haven't noticed much interaction between some cpu
hotplug work that Ashok has been posting on linux-ia64 and/or lkml, and
either of the email lists lhns-devel or linux-hotplug-devel. And I also
just noticed the thread on lkml by Keiichiro, with comments from Dave,
mentioning Matthew, hinting at additional interactions that might be
desirable between various efforts here. I even see some SGI work here.
Perhaps if I had been following this for a while, it would all make sense.
But I haven't been, and it doesn't.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
-------------------------------------------------------
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
WARNING: multiple messages have this Message-ID (diff)
From: Paul Jackson <pj@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Who's doing what with cpu/memory/node hotplug?
Date: Thu, 13 May 2004 03:51:07 +0000 [thread overview]
Message-ID: <20040512205107.16bb82a6.pj@sgi.com> (raw)
Could someone explain to me who's doing what with cpu, memory and node hotplug?
In particular, I haven't noticed much interaction between some cpu
hotplug work that Ashok has been posting on linux-ia64 and/or lkml, and
either of the email lists lhns-devel or linux-hotplug-devel. And I also
just noticed the thread on lkml by Keiichiro, with comments from Dave,
mentioning Matthew, hinting at additional interactions that might be
desirable between various efforts here. I even see some SGI work here.
Perhaps if I had been following this for a while, it would all make sense.
But I haven't been, and it doesn't.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next reply other threads:[~2004-05-13 3:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 3:51 Paul Jackson [this message]
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:23 ` Dave Hansen
2004-05-13 4:44 ` Ashok Raj
2004-05-13 4:44 ` Ashok Raj
2004-05-13 4:59 ` Paul Jackson
2004-05-13 4:59 ` Paul Jackson
2004-05-13 6:35 ` Keiichiro Tokunaga
2004-05-13 6:35 ` Keiichiro Tokunaga
2004-05-13 6:50 ` Dave Hansen
2004-05-13 6:50 ` Dave Hansen
2004-05-13 7:18 ` Paul Jackson
2004-05-13 7:18 ` Paul Jackson
2004-05-13 14:00 ` Jack Steiner
2004-05-13 14:00 ` Jack Steiner
2004-05-13 16:01 ` Dave Hansen
2004-05-13 16:01 ` Dave Hansen
2004-05-13 16:33 ` Jack Steiner
2004-05-13 16:33 ` Jack Steiner
2004-05-14 1:14 ` Keiichiro Tokunaga
2004-05-14 1:14 ` Keiichiro Tokunaga
2004-05-14 13:49 ` Russ Anderson
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=20040512205107.16bb82a6.pj@sgi.com \
--to=pj@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.