dma_resv_wait_timeout(9)
π 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, seeenum 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 β-ERESTARTSYSis the "I got interrupted" one,0means 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 π:
Reservation Object Overview(9)dma_resv_init(9)dma_resv_fini(9)dma_resv_reserve_fences(9)dma_resv_reset_max_fences(9)dma_resv_add_fence(9)dma_resv_replace_fences(9)dma_resv_iter_first_unlocked(9)dma_resv_iter_next_unlocked(9)dma_resv_iter_first(9)dma_resv_iter_next(9)dma_resv_copy_fences(9)dma_resv_get_fences(9)dma_resv_get_singleton(9)dma_resv_set_deadline(9)dma_resv_test_signaled(9)dma_resv_describe(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms