diff options
author | 2025-04-09 09:06:00 -1000 | |
---|---|---|
committer | 2025-04-09 09:06:00 -1000 | |
commit | 743354e3bb7238552cda70a5f39ba6e946a899fd (patch) | |
tree | 3dc509045c34aef6f706b1fd559392fb112d18c8 /scripts/lib/kdoc/kdoc_files.py | |
parent | sched_ext: Remove scx_ops_cpu_preempt static_key (diff) | |
download | wireguard-linux-743354e3bb7238552cda70a5f39ba6e946a899fd.tar.xz wireguard-linux-743354e3bb7238552cda70a5f39ba6e946a899fd.zip |
sched_ext: Remove scx_ops_allow_queued_wakeup static_key
scx_ops_allow_queued_wakeup is used to encode SCX_OPS_ALLOW_QUEUED_WAKEUP
into a static_key. The test is gated behind scx_enabled(), and, even when
sched_ext is enabled, is unlikely for the static_key usage to make any
meaningful difference. It is made to use a static_key mostly because there
was no reason not to. However, global static_keys can't work with the
planned hierarchical multiple scheduler support. Remove the static_key and
instead test SCX_OPS_ALLOW_QUEUED_WAKEUP directly.
In repeated hackbench runs before and after static_keys removal on an AMD
Ryzen 3900X, I couldn't tell any measurable performance difference.
Signed-off-by: Tejun Heo <tj@kernel.org>
Acked-by: Changwoo Min <changwoo@igalia.com>
Acked-by: Andrea Righi <arighi@nvidia.com>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_files.py')
0 files changed, 0 insertions, 0 deletions