public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Stuart Longland <stuartl@longlandclan.hopto.org>
Cc: lgb@lgb.hu, Fabian.Frederick@prov-liege.be, linux-kernel@vger.kernel.org
Subject: Re: 2.7 thoughts
Date: Fri, 10 Oct 2003 16:27:22 +0200	[thread overview]
Message-ID: <20031010162722.3cd1813f.skraw@ithnet.com> (raw)
In-Reply-To: <3F86BD0E.4060607@longlandclan.hopto.org>

On Sat, 11 Oct 2003 00:07:10 +1000
Stuart Longland <stuartl@longlandclan.hopto.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Stephan von Krawczynski wrote:
> 
> > You are obviously not quite familiar with industrial boxes where this is
> > state-of-the-art. 
>  >
>  > [...]
>  >
> > Generally spoken every part of a computer should be thought of as a
> > "resource" that can be added or removed at any time during runtime. CPU or
> > RAM is in no way different.
>
> Hotplug RAM I could see would be possible, but hotplug CPUs?  I spose if 
> you've got a multiprocessor box, you could swap them one at a time, but 
> my thinking is that this would cause issues with the OS as it wouldn't 
> be expecting the CPU to suddenly disappear.  Problems would be even 
> worse if the old and new CPUs were of different types too.

I wouldn't expect a hotplug feature for differing CPU types actually. But in
fact there are boxes out there that complain via phonecall that a processor
board just died and request replacement. Same goes for RAM. It is obvious that
no feature like this exists on desktop nowadays, but 2.7 and release of 2.8 is
far ahead, so I see no good reason why people should not be enabled to do this
- _then_ .
In fact it is sounds really simple to plug in additional boards to a numa-type
box. Boards meaning RAM+CPU.
HP builds hotplug PCI stuff in comparably cheap boxes, so this is not
completely off-reality.
 
> Hotplug RAM would also be interesting, but then again, I spose the 
> procedure would be to alert the kernel that the memory area from byte X 
> to byte Y would disappear, so it could page that out to swapspace.

This direction sounds likely.

Regards,
Stephan

  reply	other threads:[~2003-10-10 14:27 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-09  8:08 2.7 thoughts 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 [this message]
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
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
  -- strict thread matches above, loose matches on Subject: below --
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=20031010162722.3cd1813f.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=Fabian.Frederick@prov-liege.be \
    --cc=lgb@lgb.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stuartl@longlandclan.hopto.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