Re: [RFC PATCH v2 0/2] Saving power by cpu evacuation sched_max_capacity_pct=n

[Peter Zijlstra <a.p.zijlstra@chello.nl>]

On Wed, 2009-05-13 at 17:01 +0200, Andi Kleen wrote:
> > >From what I've been told its popular to over-commit the cooling capacity
> > in a rack, so that a number of servers can run at full thermal capacity
> > but not all.
> 
> Yes. But in this case you don't want to use throttling, you want
> to use p-states which actually safe power unlike throttling.
> 
> > I've also been told that hardware sucks at throttling, 
> 
> Throttling is not really something you should use in normal 
> operation, it's just a emergency measure. For that it works
> quite well, but you really don't want it in normal operation.
> 
> > therefore people
> > want to fix the OS so as to limit the thermal capacity and avoid the
> > hardware throttle from kicking in, whilst still not exceeding the rack
> > capacity or similar nonsense.
> 
> Yes that's fine and common, but you actually need to save power for this,
> which throttling doesn't do.
> 
> My understanding this work is a extension of the existing
> sched_mc_power_savings features that tries to be optionally more 
> aggressive to keep complete package idle so that package level
> power saving kicks in.
> 
> I'm just requesting that they don't call that throttling.

Ah no, this work differs in that regard in that it actually 'generates'
idle time, instead of optimizing idle time.

Therefore it takes actual cpu time away from real work, which is
throttling. Granted, one could call it limiting or similar, but
throttling is a correct name.