]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
sched_ext: Documentation: Clarify ops.dispatch() role in task lifecycle
authorAndrea Righi <arighi@nvidia.com>
Wed, 25 Mar 2026 21:21:00 +0000 (22:21 +0100)
committerTejun Heo <tj@kernel.org>
Thu, 26 Mar 2026 00:01:14 +0000 (14:01 -1000)
commita313357a346839d40b3a4dec393c71bf30cbb34c
tree024fd1a64abb44f442e21e3bd1f489be8e340913
parent6bf36c68b0a23afba108920d21c1c108f83371d6
sched_ext: Documentation: Clarify ops.dispatch() role in task lifecycle

ops.dispatch() is invoked when a CPU becomes available. This can occur
when a task voluntarily yields the CPU, exhausts its time slice, or is
preempted for other reasons.

If the task is still runnable, refilling its time slice in
ops.dispatch() (either by the BPF scheduler or the sched_ext core)
allows it to continue running without triggering ops.stopping().
However, this behavior is not clearly reflected in the current task
lifecycle diagram.

Update the diagram to better represent this interaction.

Fixes: 9465f44d2df2 ("sched_ext: Documentation: Clarify time slice handling in task lifecycle")
Cc: stable@vger.kernel.org # v6.17+
Signed-off-by: Andrea Righi <arighi@nvidia.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Documentation/scheduler/sched-ext.rst