rtlock_slowlock_locked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– rtlock_slowlock_locked(9) πŸ’–

hiii welcome to the Kernel API Manual, bestie πŸ’… this is the rtlock_slowlock_locked(9) page, and it's all about the slow path lock acquisition for RT locks β€” yes, the slow path, and no, that doesn't mean it's slacking, it means it's doing the careful part of the lock dance 🫢

✨ NAME ✨

rtlock_slowlock_locked β€” slow path lock acquisition for RT locks. That's the whole vibe: it's the slow-path lock acquisition helper for RT locks, and it's literally here to do exactly that πŸ’–

✨ SYNOPSIS ✨

void rtlock_slowlock_locked (struct rt_mutex_base *lock , struct wake_q_head *wake_q );

It returns void, so there's no return value to obsess over β€” the function just does its thing and exits the chat 😌

πŸŽ€ ARGUMENTS πŸŽ€

  • lock β€” the underlying RT mutex, aka the thing being locked. Main character energy, honestly πŸ”’πŸ‘‘
  • wake_q β€” the wake_q to wake tasks after we release the wait_lock. That's the assignment, no cap: it's the wake queue for waking tasks after the wait_lock gets released πŸ¦‹

πŸ”₯ SEE ALSO πŸ”₯

okay but fr fr, if you're poking around RT mutex slow paths, those two related pages are your next stops β€” rt_mutex_slowlock_block(9) and __rt_mutex_slowlock(9), periodt πŸ’…

xoxo, your kernel bestie πŸ’œ β€” from source ./kernel/locking, dated October 2026, page rtlock_slowlock_locked(9). mwah 😘

πŸ“¦ where this page comes from