From: Ingo Oeser <ioe-lkml@rameria.de>
To: linux-kernel@vger.kernel.org
Cc: Andi Kleen <ak@muc.de>,
Keiichiro Tokunaga <tokunaga.keiich@jp.fujitsu.com>
Subject: Re: [ANNOUNCE] [PATCH] Node Hotplug Support
Date: Sat, 8 May 2004 20:00:17 +0200 [thread overview]
Message-ID: <200405082000.23118.ioe-lkml@rameria.de> (raw)
In-Reply-To: <m34qqshx31.fsf@averell.firstfloor.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 07 May 2004 21:10, Andi Kleen wrote:
> Admittedly there would still need to be some coordination in case you
> would want to remove a whole building block of your machine like
> you said. An nice way to do this would be to add an atomic "to be removed"
> state to the individual unregister mechanisms that prevents the
> device from being reregistered until removed.
This is also needed for "to be replaced" state.
Imagine a node with b0rken CPU, where you still like to use its memory.
Both states can be the same actually ;-)
Regards
Ingo Oeser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAnSA1U56oYWuOrkARAnjYAJ9CfcVGC9GnqlmvSpwRzI10jj7WGwCguKYq
qtawhKJiy/j8r0d3qfqBrSw=
=Z+oX
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-05-08 18:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1TfLX-4M4-9@gated-at.bofh.it>
2004-05-07 19:10 ` Andi Kleen
2004-05-08 18:00 ` Ingo Oeser [this message]
2004-05-10 2:17 ` Keiichiro Tokunaga
2004-05-10 19:54 ` Andi Kleen
2004-05-07 15:39 Keiichiro Tokunaga
2004-05-07 15:49 ` Dave Hansen
2004-05-10 1:47 ` Keiichiro Tokunaga
2004-05-10 5:45 ` Dave Hansen
2004-05-13 1:27 ` Keiichiro Tokunaga
2004-05-13 2:04 ` Dave Hansen
2004-05-13 6:35 ` Keiichiro Tokunaga
2004-05-07 16:16 ` Martin J. Bligh
2004-05-10 2:03 ` Keiichiro Tokunaga
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=200405082000.23118.ioe-lkml@rameria.de \
--to=ioe-lkml@rameria.de \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tokunaga.keiich@jp.fujitsu.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®