mirror of
https://github.com/torvalds/linux.git
synced 2026-05-31 10:33:41 +02:00
sched_ext: Improve SCX_KF_DISPATCH comment
The comment for SCX_KF_DISPATCH was incomplete and didn't explain that ops.dispatch() may temporarily release the rq lock, allowing ENQUEUE and SELECT_CPU operations to be nested inside DISPATCH contexts. Update the comment to clarify this nesting behavior and provide better context for when these operations can occur within dispatch. Acked-by: Andrea Righi <arighi@nvidia.com> Signed-off-by: Tejun Heo <tj@kernel.org>
This commit is contained in:
parent
c8191ee8e6
commit
edf005fa27
|
|
@ -108,7 +108,11 @@ enum scx_kf_mask {
|
|||
SCX_KF_UNLOCKED = 0, /* sleepable and not rq locked */
|
||||
/* ENQUEUE and DISPATCH may be nested inside CPU_RELEASE */
|
||||
SCX_KF_CPU_RELEASE = 1 << 0, /* ops.cpu_release() */
|
||||
/* ops.dequeue (in REST) may be nested inside DISPATCH */
|
||||
/*
|
||||
* ops.dispatch() may release rq lock temporarily and thus ENQUEUE and
|
||||
* SELECT_CPU may be nested inside. ops.dequeue (in REST) may also be
|
||||
* nested inside DISPATCH.
|
||||
*/
|
||||
SCX_KF_DISPATCH = 1 << 1, /* ops.dispatch() */
|
||||
SCX_KF_ENQUEUE = 1 << 2, /* ops.enqueue() and ops.select_cpu() */
|
||||
SCX_KF_SELECT_CPU = 1 << 3, /* ops.select_cpu() */
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user