All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Lhns-devel] Re: Who's doing what with cpu/memory/node hotplug?
Date: Mon, 17 May 2004 15:52:11 +0000	[thread overview]
Message-ID: <1084809130.24128.6199.camel@nighthawk> (raw)
In-Reply-To: <20040513150842.22F5.YGOTO@us.fujitsu.com>

On Mon, 2004-05-17 at 01:38, Matthias Fouquet-Lapar wrote:
> I think I'm not quite sure why you need hotplug to balance CPUs between
> partitons. (You are not moving physical components for this, right ?)

Right, there is no movement of physical components. But, from Linux's
perspective, it really doesn't matter.  There is a cpu that I'm using,
it won't be there in a minute, I better stop using it.  That means that
Linux has to be careful with things like the for_each_cpu().   Take a
look at the calls to hotcpu_notifier() for more things that we keep an
eye on when CPUs go down.

That's pretty much what the CPU hotplug code does, and *that* doesn't
change whether the CPUs are real or more virtualized.

> > Remember, chips designs like the POWER4 tend to have a lot of cost and
> > design overhead in error correction and detection that are quite absent
> > from consumer type cpus.
> 
> Taken beside which CPU architecture has best the RAS features :-), which are
> CPU error types on ppc64 (besides cache SBE etc) which allow gracefully
> recovery (i.e. the OS continues operating and non-affected user processes
> continue to run) and hotplug replacement 

Sorry, I'm just a software guy.  No one tells me such things :)  

Rusty, have I butchered explaining CPU hotplug enough for you to step
in, yet?

-- Dave



-------------------------------------------------------
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: Dave Hansen <haveblue@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Lhns-devel] Re: Who's doing what with cpu/memory/node hotplug?
Date: Mon, 17 May 2004 15:52:11 +0000	[thread overview]
Message-ID: <1084809130.24128.6199.camel@nighthawk> (raw)
In-Reply-To: <20040513150842.22F5.YGOTO@us.fujitsu.com>

On Mon, 2004-05-17 at 01:38, Matthias Fouquet-Lapar wrote:
> I think I'm not quite sure why you need hotplug to balance CPUs between
> partitons. (You are not moving physical components for this, right ?)

Right, there is no movement of physical components. But, from Linux's
perspective, it really doesn't matter.  There is a cpu that I'm using,
it won't be there in a minute, I better stop using it.  That means that
Linux has to be careful with things like the for_each_cpu().   Take a
look at the calls to hotcpu_notifier() for more things that we keep an
eye on when CPUs go down.

That's pretty much what the CPU hotplug code does, and *that* doesn't
change whether the CPUs are real or more virtualized.

> > Remember, chips designs like the POWER4 tend to have a lot of cost and
> > design overhead in error correction and detection that are quite absent
> > from consumer type cpus.
> 
> Taken beside which CPU architecture has best the RAS features :-), which are
> CPU error types on ppc64 (besides cache SBE etc) which allow gracefully
> recovery (i.e. the OS continues operating and non-affected user processes
> continue to run) and hotplug replacement 

Sorry, I'm just a software guy.  No one tells me such things :)  

Rusty, have I butchered explaining CPU hotplug enough for you to step
in, yet?

-- Dave


  parent reply	other threads:[~2004-05-17 15:52 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-14  0:13 [Lhns-devel] Re: Who's doing what with cpu/memory/node hotplug? Yasunori Goto
2004-05-14  0:13 ` Yasunori Goto
2004-05-14  1:06 ` Paul Jackson
2004-05-14  1:06   ` Paul Jackson
2004-05-14  1:28 ` Dave Hansen
2004-05-14  1:28   ` Dave Hansen
2004-05-14  2:09 ` Jesse Barnes
2004-05-14  2:09   ` Jesse Barnes
2004-05-14  3:02 ` Keiichiro Tokunaga
2004-05-14  3:02   ` Keiichiro Tokunaga
2004-05-14  3:21 ` Dave Hansen
2004-05-14  3:21   ` Dave Hansen
2004-05-17  2:34 ` Kenji Kaneshige
2004-05-17  2:34   ` Kenji Kaneshige
2004-05-17  5:31 ` Dave Hansen
2004-05-17  5:31   ` Dave Hansen
2004-05-17  7:35 ` Matthias Fouquet-Lapar
2004-05-17  7:35   ` Matthias Fouquet-Lapar
2004-05-17  8:23 ` Dave Hansen
2004-05-17  8:23   ` Dave Hansen
2004-05-17  8:38 ` Matthias Fouquet-Lapar
2004-05-17  8:38   ` Matthias Fouquet-Lapar
2004-05-17 15:45 ` Grant Grundler
2004-05-17 15:45   ` Grant Grundler
2004-05-17 15:52 ` Dave Hansen [this message]
2004-05-17 15:52   ` Dave Hansen
2004-05-17 16:00 ` Ashok Raj
2004-05-17 16:00   ` Ashok Raj
2004-05-17 19:15 ` Matthias Fouquet-Lapar
2004-05-17 19:15   ` Matthias Fouquet-Lapar
2004-05-17 23:01 ` Matthew Dobson
2004-05-17 23:01   ` Matthew Dobson
2004-05-17 23:18 ` Luck, Tony
2004-05-17 23:18   ` Luck, Tony
2004-05-17 23:28 ` Dave Hansen
2004-05-17 23:28   ` Dave Hansen
2004-05-17 23:36 ` Jesse Barnes
2004-05-17 23:36   ` Jesse Barnes
2004-05-17 23:54 ` Grant Grundler
2004-05-17 23:54   ` Grant Grundler
2004-05-18 14:58 ` Russ Anderson
2004-05-18 20:16 ` Ashok Raj
2004-05-18 20:16   ` Ashok Raj
2004-05-18 21:01 ` Jack Steiner
2004-05-18 21:01   ` Jack Steiner
2004-05-18 21:05 ` Andi Kleen
2004-05-18 21:05   ` Andi Kleen
2004-05-18 21:12 ` Greg KH
2004-05-18 21:12   ` Greg KH
2004-05-19  5:25 ` Matthias Fouquet-Lapar
2004-05-19  5:25   ` Matthias Fouquet-Lapar
2004-05-19  9:17 ` Paul Jackson
2004-05-19  9:17   ` Paul Jackson
2004-05-19  9:30 ` Matthias Fouquet-Lapar
2004-05-19  9:30   ` Matthias Fouquet-Lapar
2004-05-19 10:22 ` Paul Jackson
2004-05-19 10:22   ` Paul Jackson
2004-05-19 14:40 ` Howell, David P
2004-05-19 14:40   ` Howell, David P
2004-05-19 14:56 ` Matthias Fouquet-Lapar
2004-05-19 14:56   ` Matthias Fouquet-Lapar

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=1084809130.24128.6199.camel@nighthawk \
    --to=haveblue@us.ibm.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.