Re: [RFD PATCH 0/4] cpu: Bulk CPU Hotplug support.

[Peter Zijlstra]

On Wed, 2009-06-17 at 17:07 +0200, Ingo Molnar wrote:
> * Paul E. McKenney <paulmck@xxxxxxxxxxxxxxxxxx> wrote:
> 
> > On Wed, Jun 17, 2009 at 09:32:57AM +0200, Peter Zijlstra wrote:
> > > On Tue, 2009-06-16 at 13:37 +0530, Vaidyanathan Srinivasan wrote:
> > > > * Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> [2009-06-15 23:23:18]:
> > > > 
> > > > > On Tue, 16 Jun 2009 11:08:39 +0530 Gautham R Shenoy <ego@xxxxxxxxxx> wrote:
> > > > > 
> > > > > > Currently on a ppc64 box with 16 CPUs, the time taken for
> > > > > > a individual cpu-hotplug operation is as follows.
> > > > > > 
> > > > > >     # time echo 0 > /sys/devices/system/cpu/cpu2/online
> > > > > >     real    0m0.025s
> > > > > >     user    0m0.000s
> > > > > >     sys     0m0.002s
> > > > > > 
> > > > > >     # time echo 1 > /sys/devices/system/cpu/cpu2/online
> > > > > >     real    0m0.021s
> > > > > >     user    0m0.000s
> > > > > >     sys     0m0.000s
> > > > > 
> > > > > Surprised.  Do people really online and offline CPUs frequently enough
> > > > > for this to be a problem?
> > > > 
> > > > Certainly not for hardware faults or hardware replacement, but
> > > > cpu-hotplug interface is useful for changing system configuration to
> > > > meet different objectives like
> > > > 
> > > > * Reduce system capacity to reduce average power and reduce heat
> > > > 
> > > > * Increasing number of cores and threads in a CPU package is leading
> > > >   to multiple cpu offline/online operations for any perceivable effect
> > > > 
> > > > * Dynamically change CPU configurations in virtualized environments
> > > 
> > > I tend to agree with Andrew, if any of those things are done 
> > > frequent enough that the hotplug performance matter you're doing 
> > > something mighty odd.
> > 
> > Boot speedup?
> 
> Also, if it brings more attention (and more stability and more 
> bugfixes) to CPU hotplug that's only good.

Sure, but do we need the extra complexity?

I mean, sure bootup speed might be nice, but any of the scenarios given
should simply not require cpu hotplug actions of a frequent enough
nature that any performance matters.

If you want to switch off all SMT siblings you don't do that 50 times a
second, you do that once per bootup or something.

Furthermore we already established that cpu hotlpug is not the proper
interface for thermal management, and dynamically changing virtualized
muck isn't something you do at 100Hz either.

So what worries me is the justification for this work. It might be good
and nice, but if the reasons are wrong it still worries me.

So again, why? -- the bootup thing is the only sane answer so far.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/