[RFCv4 PATCH 32/34] sched: Consider a not over-utilized energy-aware system as balanced

From: Morten Rasmussen
Date: Tue May 12 2015 - 15:40:18 EST

From: Dietmar Eggemann <dietmar.eggemann@xxxxxxx>

In case the system operates below the tipping point indicator,
introduced in ("sched: Add over-utilization/tipping point
indicator"), bail out in find_busiest_group after the dst and src
group statistics have been checked.

There is simply no need to move usage around because all involved
cpus still have spare cycles available.

For an energy-aware system below its tipping point, we rely on the
task placement of the wakeup path. This works well for short running

The existence of long running tasks on one of the involved cpus lets
the system operate over its tipping point. To be able to move such
a task (whose load can't be used to average the load among the cpus)
from a src cpu with lower capacity than the dst_cpu, an additional
rule has to be implemented in need_active_balance.

Signed-off-by: Dietmar Eggemann <dietmar.eggemann@xxxxxxx>
kernel/sched/fair.c | 4 ++++
1 file changed, 4 insertions(+)

diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index fe41e1e..83218e0 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -7340,6 +7340,10 @@ static struct sched_group *find_busiest_group(struct lb_env *env)
* this level.
update_sd_lb_stats(env, &sds);
+ if (energy_aware() && !env->dst_rq->rd->overutilized)
+ goto out_balanced;
local = &sds.local_stat;
busiest = &sds.busiest_stat;


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/