public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Stuart Longland <stuartl@longlandclan.hopto.org>
Cc: Stephan von Krawczynski <skraw@ithnet.com>,
	lgb@lgb.hu, Fabian.Frederick@prov-liege.be,
	linux-kernel@vger.kernel.org
Subject: Re: 2.7 thoughts
Date: Thu, 16 Oct 2003 05:15:00 +1000	[thread overview]
Message-ID: <20031015191500.GI610@krispykreme> (raw)
In-Reply-To: <3F86BD0E.4060607@longlandclan.hopto.org>

 
> 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.

Our ppc64 hardware supports hotswap cpu - not physically adding a cpu but
rather moving the pool of cpus into and out of partitions.

There are many uses for cpu hotplug. If you hit a threshold of
correctible errors on a cpu, we can remove the failing cpu and swap in a
spare if available. If we do this before we get a UE then all is good.
One day we can get even more intelligent and recover from certain UEs, I
was talking to Andi and the ia64 guys at OLS about this (eg UE in a cpu
array mapped to a userspace address, we can kill the task and continue
on).

You can also move cpus between partitions on the fly, moving cpus out of
idle partitions and into the busy ones.

Anton

  parent reply	other threads:[~2003-10-15 23:35 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
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 [this message]
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=20031015191500.GI610@krispykreme \
    --to=anton@samba.org \
    --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 \
    /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