sched/fair: remove util_est boosting
There is no need to use runnable_avg when estimating util_est and that
even generates wrong behavior because one includes blocked tasks whereas
the other one doesn't. This can lead to accounting twice the waking task p,
once with the blocked runnable_avg and another one when adding its
util_est.
cpu's runnable_avg is already used when computing util_avg which is then
compared with util_est.
In some situation, feec will not select prev_cpu but another one on the
same performance domain because of higher max_util
Fixes: 7d0583cf9e
("sched/fair, cpufreq: Introduce 'runnable boosting'")
Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
Tested-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
Link: https://lore.kernel.org/r/20230706135144.324311-1-vincent.guittot@linaro.org
This commit is contained in:
parent
752182b24b
commit
c2e164ac33
|
@ -7320,9 +7320,6 @@ cpu_util(int cpu, struct task_struct *p, int dst_cpu, int boost)
|
||||||
|
|
||||||
util_est = READ_ONCE(cfs_rq->avg.util_est.enqueued);
|
util_est = READ_ONCE(cfs_rq->avg.util_est.enqueued);
|
||||||
|
|
||||||
if (boost)
|
|
||||||
util_est = max(util_est, runnable);
|
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* During wake-up @p isn't enqueued yet and doesn't contribute
|
* During wake-up @p isn't enqueued yet and doesn't contribute
|
||||||
* to any cpu_rq(cpu)->cfs.avg.util_est.enqueued.
|
* to any cpu_rq(cpu)->cfs.avg.util_est.enqueued.
|
||||||
|
|
Loading…
Reference in New Issue