scx_bypass_dsp_enabled(9)

🦋 scx_bypass_dsp_enabled(9) — Kernel API Manual 🌈

✨ NAME ✨

scx_bypass_dsp_enabled — bestie, this one checks if the bypass dispatch path is enabled 💅

🎀 SYNOPSIS 🎀

bool scx_bypass_dsp_enabled (struct scx_sched *sch );

💖 ARGUMENTS 💖

• sch — the scheduler to check, obviously 👑

🌸 DESCRIPTION 🌸

Okay so when a descendant scheduler enters bypass mode 😭, the bypassed tasks get scheduled by the nearest non-bypassing ancestor — or by the root scheduler if literally all the ancestors are bypassing. In the former case, that ancestor is not itself bypassing, but its bypass DSQs are gonna be populated with bypassed tasks from descendants. So its bypass dispatch path must be active, even though its own bypass_depth remains zero. No cap 🫶

This function checks bypass_dsp_enable_depth, which is managed separately from bypass_depth to enable this decoupling. It's giving separation of concerns, fr fr ✨ See enable_bypass_dsp and scx_disable_bypass_dsp.

🦋 SEE ALSO 🦋

• Kernel file: ./kernel/sched/ext/internal.h 📁
• scx_add_event(9)
• __scx_add_event(9)
• struct scx_enable_args(9)
• struct sched_ext_ops(9)
• struct sched_ext_ops_cid(9)
• scx_arena_to_kaddr(9)
• scx_kaddr_to_arena(9)
• DEFINE_SCX_COMPAT_MARKER(9)
• scx_root_protected_live(9)
• scx_root_protected(9)
• scx_ops_sanitize_err(9)
• scx_has_subs(9)
• scx_task_sched(9)
• scx_task_sched_rcu(9)
• scx_task_on_sched(9)
• scx_prog_sched(9)
• scx_parent(9)

source: ./kernel/sched/ext · date: October 2026 · manual: scx_bypass_dsp_enabled(9) — okay bye bestie, go read the source 💅✨