futex_cmp_requeue_pi(9)

📦 version 7.3.1, in nixpkgs unstable

🦋 futex_cmp_requeue_pi(9) 🦋

okay bestie, so this is a page straight out of the Kernel API Manual, and it's literally called futex_cmp_requeue_pi — yes that's a whole mouthful, yes we're gonna get through it together 💖

✨ NAME ✨

futex_cmp_requeue_pi — requeue tasks from uaddr to uaddr2 (PI aware)

like... it moves tasks from one futex to another and it knows about priority inheritance. main character behaviour tbh 👑

🌸 SYNOPSIS 🌸

int futex_cmp_requeue_pi (futex_t *uaddr , futex_t val , futex_t *uaddr2
, int nr_wake , int nr_requeue , int opflags );

look at her. six whole arguments. she's doing the most and honestly? she's slaying 💅

🎀 ARGUMENTS 🎀

  • uaddr — the non-PI futex source, aka where everybody's currently vibing 🫶
  • val — hmm. the manual literally just says -- undescribed -- so bestie... nobody wrote anything 😭 ngl we're all just out here not knowing. fr fr that's the whole description.
  • uaddr2 — the PI futex target, aka the destination. the glow-up location ✨
  • nr_wake — wake up to this many tasks. that's the cap, no cap 🌈
  • nr_requeue — requeue up to this many tasks. again, a limit, not a suggestion 🌸
  • opflags — another -- undescribed -- 🫠 like the manual simply did not elaborate. iconic of it, honestly.
lowkey two of these arguments have zero documentation and I'm just the messenger 💀 I'm not gonna invent lore for them. we report what the page says and we move on.

👑 SEE ALSO 👑

that's fifteen friends and one file path, and every single one of them ate 🔥 go read them all, iykyk 💜

okay that's the whole page, bestie 🎀 this little cutie comes from ./tools/testing/selftests/fute... and the date on her is October 2026 — so yes, she's from the future, and she's still futex_cmp_requeue_pi(9) 💖 periodt.

📦 where this page comes from