Skip to content

Conversation

@multics69
Copy link
Contributor

Managing pinned tasks in a per-CPU DSQ is advantageous. When pinned tasks are on the shared per-domain DSQ, it takes longer to pop a task from the DSQ because the CPU must skip pinned tasks that cannot be executed on the CPU. That stretches the critical section, increasing the contention on the shared DSQ. So, let's avoid this problem by managing per-CPU DSQ for pinned tasks.

Managing pinned tasks in a per-CPU DSQ is advantageous. When pinned tasks
are on the shared per-domain DSQ, it takes longer to pop a task from the
DSQ because the CPU must skip pinned tasks that cannot be executed on the
CPU. That stretches the critical section, increasing the contention on the
shared DSQ. So, let's avoid this problem by managing per-CPU DSQ for pinned
tasks.

Signed-off-by: Changwoo Min <changwoo@igalia.com>
Copy link
Contributor

@hodgesds hodgesds left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@multics69 multics69 added this pull request to the merge queue Nov 23, 2025
Merged via the queue into sched-ext:main with commit c54f715 Nov 23, 2025
41 of 44 checks passed
@multics69 multics69 deleted the lavd-pinned-slice-us-default branch November 23, 2025 09:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants