From: Mark Mielke <mark@mark.mielke.cc>
To: William Lee Irwin III <wli@holomorphy.com>,
G?bor L?n?rt <lgb@lgb.hu>,
Stuart Longland <stuartl@longlandclan.hopto.org>,
Stephan von Krawczynski <skraw@ithnet.com>,
Fabian.Frederick@prov-liege.be, linux-kernel@vger.kernel.org
Subject: Re: 2.7 thoughts
Date: Fri, 10 Oct 2003 10:48:37 -0400 [thread overview]
Message-ID: <20031010144837.GB12134@mark.mielke.cc> (raw)
In-Reply-To: <20031010144723.GC727@holomorphy.com>
On Fri, Oct 10, 2003 at 07:47:23AM -0700, William Lee Irwin III wrote:
> On Fri, Oct 10, 2003 at 04:35:29PM +0200, G?bor L?n?rt wrote:
> > Why? Sure, you should note OS before unplug a CPU ;-) but in this case OS
> > should be noticed that it could not use that CPU any more (like scheduler,
> > interrupt delivering etc). And then it's not an issue if you unplug THAT
> > cpu. Sure, some hw supporting is needed, a "normal" motherboard does not
> > like to unplug a CPU when powered of course by hardware issues, but "CPU
> > hotplug capable" motherboards can support this. Maybe of course some notice
> > mechanism is needed for the motherboard as well not only for the OS, but it
> > only mean that notfication before unplugging the CPU should be delivered to
> > the OS _and_ to the hardware. Sure, I have no experience at all in this
Perhaps I've naive here, but - with hot-pluggable CPU machines, do you not
de-activate the CPU through software first, before pulling the CPU out, at
which point it is not in use?
mark
--
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
next prev parent reply other threads:[~2003-10-10 14:50 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 8:08 Frederick, Fabian
2003-10-09 8:55 ` John Bradford
2003-10-09 9:45 ` mario noioso
2003-10-09 11:58 ` Gábor Lénárt
2003-10-09 14:57 ` Stephan von Krawczynski
2003-10-10 6:19 ` Stuart Longland
2003-10-10 6:30 ` William Lee Irwin III
2003-10-10 7:30 ` YoshiyaETO
2003-10-10 7:40 ` William Lee Irwin III
2003-10-10 8:47 ` YoshiyaETO
2003-10-10 9:09 ` William Lee Irwin III
2003-10-10 10:26 ` YoshiyaETO
2003-10-10 10:50 ` William Lee Irwin III
2003-10-10 10:55 ` William Lee Irwin III
2003-10-10 10:51 ` Stephan von Krawczynski
2003-10-10 14:07 ` Stuart Longland
2003-10-10 14:27 ` Stephan von Krawczynski
2003-10-10 14:35 ` Gábor Lénárt
2003-10-10 14:47 ` William Lee Irwin III
2003-10-10 14:48 ` Mark Mielke [this message]
2003-10-10 15:01 ` William Lee Irwin III
2003-10-10 15:50 ` Mark Mielke
2003-10-10 16:35 ` Chris Friesen
2003-10-10 16:44 ` William Lee Irwin III
2003-10-12 20:14 ` Pavel Machek
2003-10-10 15:12 ` Jamie Lokier
2003-10-10 15:21 ` William Lee Irwin III
2003-10-10 18:03 ` Tim Hockin
2003-10-10 18:29 ` William Lee Irwin III
2003-10-10 18:56 ` Tim Hockin
2003-10-10 23:40 ` Rusty Russell
2003-10-15 19:15 ` Anton Blanchard
2003-10-10 13:30 ` Kevin Corry
2003-10-10 18:29 ` Lars Marowsky-Bree
2003-10-11 3:49 ` jw schultz
2003-10-11 13:24 ` Lars Marowsky-Bree
2003-10-11 19:50 ` jw schultz
2003-10-10 17:12 ` Matt Simonsen
2003-10-10 20:59 ` Pedro Larroy
2003-10-09 18:17 ` Greg KH
2003-10-09 19:07 ` Pavel Machek
2003-10-09 11:56 Svetoslav Slavtchev
2003-10-09 12:44 Xose Vazquez Perez
2003-10-09 13:17 Frederick, Fabian
2003-10-09 13:19 ` Jens Axboe
2003-10-09 13:50 ` Gábor Lénárt
2003-10-09 13:52 ` Bartlomiej Zolnierkiewicz
2003-10-10 19:01 Zwane Mwaikambo
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=20031010144837.GB12134@mark.mielke.cc \
--to=mark@mark.mielke.cc \
--cc=Fabian.Frederick@prov-liege.be \
--cc=lgb@lgb.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.com \
--cc=stuartl@longlandclan.hopto.org \
--cc=wli@holomorphy.com \
/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
all inboxes | Powered by JetHome®