scx_rescue_accrue(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… scx_rescue_accrue β€” the Kernel API Manual, bestie edition

okay so you're looking at scx_rescue_accrue(9) from the Kernel API Manual and honestly? it's giving "tiny function, big responsibilities." let's get into it πŸŽ€


✨ NAME ✨

scx_rescue_accrue β€” accrue budget at the configured fraction of elapsed time. that's it, that's the whole job, and she does it flawlessly πŸ’…


🌸 SYNOPSIS 🌸

void scx_rescue_accrue (struct rq *rq );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • rq β€” the rq of interest, aka the runqueue you're being nosy about πŸ‘€

πŸ’– DESCRIPTION πŸ’–

okay so picture this: a session spans from the first arrival until no rescuee is left β€” pending or admitted, like literally none, zero, gone 🫢

while a session is active, the cap is three quanta, and the balance is what drives escalation. (see scx_rescue_timerfn if you wanna know more about that whole situation β€” iykyk ✨)

but outside a session? the cap is just one quantum. so an idle gap funds the next arrival's admission, but it never, ever funds an escalation. no cap, no escalation, that's the rule periodt πŸ’€

lowkey the whole vibe is: sessions get the fancy three-quantum budget, idle gaps get one quantum and only for admission. do not mix them up bestie, the math will not forgive you 😭

🧚 SEE ALSO 🧚

kernel file ./kernel/sched/ext/sub.c β€” and the whole friend group:


that's the whole page!! 🌈 shipped from ./kernel/sched/ext, dated October 2026, under the name scx_rescue_accrue(9) β€” go accrue that budget and slay, bestie πŸ‘‘

πŸ“¦ where this page comes from