futex_wait_requeue_pi(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

Okay bestie, this is futex_wait_requeue_pi(9) from the Kernel API Manual β€” and it is literally the setup half of the requeue_pi situation. πŸ’…βœ¨

πŸŽ€ NAME πŸŽ€

futex_wait_requeue_pi β€” block on uaddr and prepare to requeue to uaddr2

✨ SYNOPSIS ✨

int futex_wait_requeue_pi (futex_t *uaddr , futex_t
       *uaddr2 , struct timespec *timeout , int opflags );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • uaddr β€” non-PI futex source. That’s the vibe.
  • val β€” the page literally says -- undescribed -- 😭 no extra lore given.
  • uaddr2 β€” PI futex target. Main character target energy.
  • timeout β€” also -- undescribed --. The manpage is gatekeeping, ngl.
  • opflags β€” yep, -- undescribed -- again. πŸ™ˆ

πŸ’… DESCRIPTION πŸ’…

This is the first half of the requeue_pi mechanism. It shall always be paired with futex_cmp_requeue_pi β€” periodt, do not run it solo. 🫢

πŸ‘‘ SEE ALSO πŸ‘‘

The futex fam and friends, fr fr:


Signed, sealed, delivered: futex_wait_requeue_pi(9), from the ./tools/testing/selftests/fute... source/version, dated October 2026. Stay futexy, bestie πŸ’–πŸŒΈ

πŸ“¦ where this page comes from