dma_resv_iter_next_unlocked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ dma_resv_iter_next_unlocked(9) ✨

okay so bestie, welcome to the Kernel API Manual πŸ’… this one's a function page, and yes it's a whole vibe.


πŸŽ€ NAME πŸŽ€

dma_resv_iter_next_unlocked β€” get the next fence in an unlocked dma_resv obj. literally that's the whole thing, no cap πŸ’–


🌸 SYNOPSIS 🌸

struct dma_fence * dma_resv_iter_next_unlocked (struct dma_resv_iter
*cursor );

look at that signature bestie, it's giving "one pointer in, one pointer out" πŸ¦‹


⭐ ARGUMENTS ⭐

  • cursor β€” the cursor you're holding, like, the one that's currently sitting at the current position πŸ“ that's it, that's the arg.

πŸ”₯ DESCRIPTION πŸ”₯

okay so this returns the next fence from an unlocked dma_resv obj. simple, right? but listen πŸ‘€

⚠️ Beware β€” the iterator can be restarted. so if your code is out here accumulating statistics or doing anything ~similar~, you have to check for that with dma_resv_iter_is_restarted. no cap, don't sleep on this one 😭

and for that exact reason, the manpage is like: prefer the locked dma_resv_iter_next whenever possible. like, whenever. it's right there. use it. πŸ’…

so yeah β€” next fence from an unlocked dma_resv obj, but mind the restart, bestie 🫢


🌈 SEE ALSO 🌈

all of these are your new besties, go say hi πŸ’œ


that's the whole page, bestie β€” sourced straight from ./drivers/dma-buf, dated October 2026, and filed under dma_resv_iter_next_unlocked(9). slay, go read the locked version, mwah πŸ’‹ πŸŽ€βœ¨

πŸ“¦ where this page comes from