scx_task_iter_relock(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ scx_task_iter_relock πŸŽ€

okay so this is a page from the Kernel API Manual, and it's about scx_task_iter_relock(9) β€” yes that's a mouthful, we'll get through it together bestie 🫢


✨ NAME ✨

scx_task_iter_relock β€” grab scx_tasks_lock back, and optionally also @p's rq while you're at it πŸ’…


🌸 SYNOPSIS 🌸

void scx_task_iter_relock (struct scx_task_iter *iter, struct task_struct *p);

πŸ¦‹ ARGUMENTS πŸ¦‹

  • iter β€” the iterator you wanna relock, bestie. that's the one.
  • p β€” the task whose rq you want locked, or NULL if you only want scx_tasks_lock and nothing else. no rq for you, just the plain lock πŸŽ€

πŸ’– DESCRIPTION πŸ’–

so this is the counterpart to scx_task_iter_unlock β€” like, the other half of the duo, the remix, the re-acquisition arc ✨

locking p's rq is optional. you can take it or leave it, no pressure, we're not like that.

once they're re-acquired though? both locks are managed by the iterator from here on out, periodt. the iterator is the main character now πŸ‘‘


πŸ”₯ SEE ALSO πŸ”₯

the kernel file lives at ./kernel/sched/ext/ext.c, and honestly the whole friend group is here, so let's do the roll call πŸ’€


and that's the whole vibe check bestie πŸ’œ this page is from the ./kernel/sched/ext corner of the kernel and it's dated October 2026 β€” go forth and relock responsibly, ily 🧚✨

πŸ“¦ where this page comes from