Re: [3/11] issue 3: No understanding of potential cpu capacity

[Rafael J. Wysocki]

On Tuesday, January 07, 2014 04:19:39 PM Morten Rasmussen wrote:
> To minimize energy it may sometimes be better to put waking tasks on
> partially loaded cpus instead of powering up more cpus (particularly if
> it implies powering up a new cluster/group of cpus with associated
> caches). To make that call, information about the potential spare cycles
> on the busy cpus is required.

That generally is not the only thing that matters.  There's one more factor
called "responsiveness" that used to be popular in the past.  It, roughly,
is about how much time it takes for the system to respond to user actions,
on the average.

> Currently, the CFS scheduler has no knowledge about frequency scaling.
> Frequency scaling governors generally try to match the frequency to
> the load, which means that the idle time has no absolute meaning. The
> potential spare cpu capacity may be much higher than indicated by the
> idle time if the cpu is running at a low P-state.
> 
> The energy trade-off may justify putting another task on a loaded cpu
> even if it causes a change to a higher P-state to handle the extra load.
> Related issues are frequency (and cpu micro architecture) invariant task
> load and power topology information, which are both needed to enable the
> scheduler for energy-aware task placement. This is covered in more
> detail in issue 5.
> 
> The potential cpu capacity cannot be assumed to be constant as thermal
> management may restrict the usage of high performance P-states
> dynamically.

That's correct.  Moreover, all of the above seems to assume that we can get
exact power numbers for all of the involved C-states and P-states.  What if
we can't?

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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/