Add the blocked utilization contribution to group sched_entity
utilization (se->avg.utilization_avg_contrib) and to get_cpu_usage().
With this change cpu usage now includes recent usage by currently
non-runnable tasks, hence it provides a more stable view of the cpu
usage. It does, however, also mean that the meaning of usage is changed:
A cpu may be momentarily idle while usage >0. It can no longer be
assumed that cpu usage >0 implies runnable tasks on the rq.
cfs_rq->utilization_load_avg or nr_running should be used instead to get
the current rq status.

cc: Ingo Molnar <[email protected]>
cc: Peter Zijlstra <[email protected]>

Signed-off-by: Morten Rasmussen <[email protected]>
---
 kernel/sched/fair.c | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 0fc8963..33d3d81 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -2761,7 +2761,8 @@ static long 
__update_entity_utilization_avg_contrib(struct sched_entity *se)
                __update_task_entity_utilization(se);
        else
                se->avg.utilization_avg_contrib =
-                                       group_cfs_rq(se)->utilization_load_avg;
+                               group_cfs_rq(se)->utilization_load_avg +
+                               group_cfs_rq(se)->utilization_blocked_avg;
 
        return se->avg.utilization_avg_contrib - old_contrib;
 }
@@ -4828,11 +4829,12 @@ static int select_idle_sibling(struct task_struct *p, 
int target)
 static int get_cpu_usage(int cpu)
 {
        unsigned long usage = cpu_rq(cpu)->cfs.utilization_load_avg;
+       unsigned long blocked = cpu_rq(cpu)->cfs.utilization_blocked_avg;
 
-       if (usage >= SCHED_LOAD_SCALE)
+       if (usage + blocked >= SCHED_LOAD_SCALE)
                return capacity_orig_of(cpu);
 
-       return usage;
+       return usage + blocked;
 }
 
 /*
-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to