mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
synced 2025-01-23 00:20:52 -05:00
sched_ext: Simplify scx_can_stop_tick() invocation in sched_can_stop_tick()
The way sched_can_stop_tick() used scx_can_stop_tick() was rather confusing and the behavior wasn't ideal when SCX is enabled in partial mode. Simplify it so that: - scx_can_stop_tick() can say no if scx_enabled(). - CFS tests rq->cfs.nr_running > 1 instead of rq->nr_running. This is easier to follow and leads to the correct answer whether SCX is disabled, enabled in partial mode or all tasks are switched to SCX. Peter, note that this is a bit different from your suggestion where sched_can_stop_tick() unconditionally returns scx_can_stop_tick() iff scx_switched_all(). The problem is that in partial mode, tick can be stopped when there is only one SCX task even if the BPF scheduler didn't ask and isn't ready for it. Signed-off-by: Tejun Heo <tj@kernel.org> Suggested-by: Peter Zijlstra <peterz@infradead.org> Acked-by: David Vernet <void@manifault.com>
This commit is contained in:
parent
0df340ceae
commit
11cc374f46
1 changed files with 2 additions and 2 deletions
|
@ -1286,10 +1286,10 @@ bool sched_can_stop_tick(struct rq *rq)
|
|||
* left. For CFS, if there's more than one we need the tick for
|
||||
* involuntary preemption. For SCX, ask.
|
||||
*/
|
||||
if (!scx_switched_all() && rq->nr_running > 1)
|
||||
if (scx_enabled() && !scx_can_stop_tick(rq))
|
||||
return false;
|
||||
|
||||
if (scx_enabled() && !scx_can_stop_tick(rq))
|
||||
if (rq->cfs.nr_running > 1)
|
||||
return false;
|
||||
|
||||
/*
|
||||
|
|
Loading…
Reference in a new issue