dma_resv_iter_next(9)
π dma_resv_iter_next(9) π
okay bestie, buckle up β this is a page straight outta the Kernel API Manual, and it's literally about grabbing the next fence out of a locked dma_resv object. tiny page, big vibes. let's go π
β¨ NAME β¨
dma_resv_iter_next β get the next fence from a locked dma_resv object. that's it, that's the whole thing π¦
β¨ SYNOPSIS β¨
struct dma_fence * dma_resv_iter_next (struct dma_resv_iter *cursor );
β¨ ARGUMENTS β¨
cursorβ the cursor β¨ this lil guy is what records the current position for you. main character energy, honestly π
β¨ DESCRIPTION β¨
so what it does: it returns the next fences from the dma_resv object β and it does that while holding the dma_resv.lock π no cap, the lock part is the whole point. hold it properly, bestie, or it's giving chaos π
β¨ SEE ALSO β¨
the whole friend group π«Ά β the kernel file ./drivers/dma-buf/dma-resv.c, plus:
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_copy_fences(9)dma_resv_get_fences(9)dma_resv_get_singleton(9)dma_resv_wait_timeout(9)dma_resv_set_deadline(9)dma_resv_test_signaled(9)dma_resv_describe(9)
ngl this one's short but it ate. locked object in, next fence out. periodt π
πΈ okay that's the page!! brought to you by ./drivers/dma-buf, dated October 2026, and signed off with love from dma_resv_iter_next(9) β stan the fence iterator, mwah πβ¨
π¦ 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