diff options
author | Aaron Lu <ziqianlu@bytedance.com> | 2025-09-10 17:50:41 +0800 |
---|---|---|
committer | Peter Zijlstra <peterz@infradead.org> | 2025-09-15 09:38:37 +0200 |
commit | fe8d238e646e16cc431b7a5899f8dda690258ee9 (patch) | |
tree | 8fe34a33c0f9e939ba5ec8f9107ae40576451798 /rust/helpers/security.c | |
parent | 5b726e9bf9544a349090879a513a5e00da486c14 (diff) |
sched/fair: Propagate load for throttled cfs_rq
Before task based throttle model, propagating load will stop at a
throttled cfs_rq and that propagate will happen on unthrottle time by
update_load_avg().
Now that there is no update_load_avg() on unthrottle for throttled
cfs_rq and all load tracking is done by task related operations, let the
propagate happen immediately.
While at it, add a comment to explain why cfs_rqs that are not affected
by throttle have to be added to leaf cfs_rq list in
propagate_entity_cfs_rq() per my understanding of commit 0258bdfaff5b
("sched/fair: Fix unfairness caused by missing load decay").
Signed-off-by: Aaron Lu <ziqianlu@bytedance.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Chengming Zhou <chengming.zhou@linux.dev>
Diffstat (limited to 'rust/helpers/security.c')
0 files changed, 0 insertions, 0 deletions