dispatch_to_local_dsq(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dispatch_to_local_dsq(9) — Kernel API Manual 🎀

okay so bestie, welcome to the Kernel API Manual page for dispatch_to_local_dsq — yes the whole manual is literally named that, we're not being weird about it, that's just how these pages roll ✨

🌸 NAME 🌸

dispatch_to_local_dsq — Dispatch a task to a local dsq 💫

✨ SYNOPSIS ✨

void dispatch_to_local_dsq (struct scx_sched *sch , struct rq *rq ,
struct scx_dispatch_q *dst_dsq , struct task_struct *p , u64 slice , u64
vtime , u64 enq_flags );

🫶 ARGUMENTS 🫶

  • sch — the scx_sched we're operating on, that's the whole vibe 💜
  • rq — the current rq, and heads up: it's locked 🔒
  • dst_dsq — the destination DSQ, aka where p is headed ✈️
  • p — the task being dispatched, our main character fr fr 👑
  • slice — the slice carried by the insert verdict; 0 keeps the current value (yes, zero is the "no change" girlie) 🙈
  • vtime — the vtime carried by the insert verdict, committed on PRIQ inserts ⏱️
  • enq_flags — SCX_ENQ_* 🏷️

💖 DESCRIPTION 💖

So picture it: we're holding the rq lock (iconic, we love a locked rq) and we want to dispatch p to dst_dsq, which is a local DSQ. This function does all the synchronization dancing that's needed, because local DSQs are protected with rq locks — so yeah, there's choreography involved, and this function is the choreographer 💃🕺

The caller must have exclusive ownership of p — like, for real, e.g. through SCX_OPSS_DISPATCHING. No sharing, no cap 🚫

⚠️ Do not come in here without exclusive ownership of p. That's the rule, bestie. The function is not gonna check your vibes for you 💀

🌈 SEE ALSO 🌈

Kernel file ./kernel/sched/ext/ext.c — and literally the entire extended universe, iykyk 🔥

and that's the page, bestie 🦋 this lil masterpiece lives in ./kernel/sched/ext, dated October 2026, and it's titled dispatch_to_local_dsq(9) — go forth and dispatch responsibly, mwah 💅💖

📦 where this page comes from