dma_resv_wait_timeout(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– dma_resv_wait_timeout(9) πŸ’–

okay so bestie, welcome to the Kernel API Manual ✨ β€” this one's all about waiting on a reservation object's fences like the patient main character you are 🫢


🌸 NAME 🌸

dma_resv_wait_timeout β€” wait on reservation's objects fences ⏳


✨ SYNOPSIS ✨

long dma_resv_wait_timeout (struct dma_resv *obj , enum dma_resv_usage
usage , bool intr , unsigned long timeout );

πŸŽ€ ARGUMENTS πŸŽ€

  • obj β€” the reservation object, aka the thing we're literally waiting on πŸ’…
  • usage β€” controls which fences to include, see enum dma_resv_usage. iykyk πŸ”₯
  • intr β€” if true, do interruptible wait (so a signal can come through and wake you up, no cap) 😭
  • timeout β€” timeout value in jiffies, or zero to return immediately πŸ•

πŸ¦‹ DESCRIPTION πŸ¦‹

Callers are not required to hold specific locks β€” but maybe hold dma_resv_lock already. πŸ‘€ That's the whole vibe check, fr fr.

⭐ RETURNS ⭐

Returns -ERESTARTSYS if interrupted, 0 if the wait timed out, or greater than zero on success. slay πŸŽ‰

ngl bestie, watch those return values β€” -ERESTARTSYS is the "I got interrupted" one, 0 means you ran out of time, and anything greater than zero means you ate and left no crumbs πŸ‘‘

🌈 SEE ALSO 🌈

Kernel file ./drivers/dma-buf/dma-resv.c, plus the whole friend group πŸ’œ:


okay that's the whole page bestie, no notes πŸ’…

source path: ./drivers/dma-buf Β· date: October 2026 Β· page: dma_resv_wait_timeout(9) β€” mwah, go wait on those fences responsibly πŸ§šπŸ’–

πŸ“¦ where this page comes from