Re: [rfc][patch] select_idle_sibling() inducing bouncing on westmere

[Mike Galbraith]

On Sun, 2012-05-27 at 07:11 -0700, Arjan van de Ven wrote: 
> On 5/27/2012 2:17 AM, Mike Galbraith wrote:
> > On Sat, 2012-05-26 at 10:27 +0200, Mike Galbraith wrote: 
> >> Hohum, back to finding out what happened to cpufreq.
> > 
> > Answer: nothing.. in mainline.
> > 
> > I test performance habitually, so just never noticed how bad ondemand
> > sucks.  In enterprise, I found the below, explaining why cores crank up
> > fine there, but not in mainline.  Somebody thumped ondemand properly on
> > it's pointy head.
> > 
> > But, check out the numbers below this, and you can see just how horrible
> > bouncing is when you add governor latency _on top_ of it. 
> 
> part of it is not ondemand, but cpufreq.
> cpufreq forces you to schedule a kernel thread to change cpu
> frequency... on the cpu that's already busy.
> God knows what the scehduler then does in terms of load balancing.

Well, it'll take a spot that could have been used to authorize an affine
wakeup for one, switch freqs a tad too late if it doesn't preempt, not
to mention munching valuable cycles.

> (yes this is one of the things that will be fixed in the code that we
> now have working internally, and we're now making sure does not regress)

Cool.

> btw, on modern Intel CPUs, where in Idle, you have a frequency of Zero,
> regardless of what you ask for when you're running, and where an idle
> cpu is clock gated.... the performance governor behaves almost the same
> as ondemand in terms of power (due to the suckitude of ondemand)... but
> much better performance.

That sounds like it should rock.

-Mike

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