"Power" is a very bad term in the scheduler context. There are so many meanings that can be attached to it. And with the upcoming "power aware" scheduler work confusion is sure to happen.
The definition of "power" is typically the rate at which work is performed, energy is converted or electric energy is transferred. The notion of "compute capacity" is rather at odds with "power" to the point many comments in the code have to make it explicit that "capacity" is the actual intended meaning. So let's make it clear what we man by using "capacity" in place of "power" directly in the code. That will make the introduction of actual "power consumption" concepts much clearer later on. This is based on the latest tip tree where scheduler changes are already queued. Note: The diffstat is not completely symetric wrt added/removed lines as some comments were reflowed. arch/arm/kernel/topology.c | 54 +++---- include/linux/sched.h | 8 +- kernel/sched/core.c | 89 ++++++----- kernel/sched/fair.c | 322 ++++++++++++++++++++------------------- kernel/sched/sched.h | 18 +-- 5 files changed, 246 insertions(+), 245 deletions(-) Nicolas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
