dma_fence_is_later_or_same(9)

💅 NAME 💅

ok so dma_fence_is_later_or_same — bestie, this is the little guy that returns true if f1 is later than or the same as f2 🫶 that's literally the whole job.

---

✨ SYNOPSIS ✨

bool dma_fence_is_later_or_same (struct dma_fence *f1 , struct dma_fence
*f2 );

like yes she's a bool-returning icon, no cap 👑

---

🎀 ARGUMENTS 🎀

• f1 — the first fence, and she's gotta be from the same context as her bestie over there 💖
• f2 — the second fence, also from the same context, we do not mix friend groups here 🚫

---

🌸 DESCRIPTION 🌸

So the vibe check is this: it returns true if f1 is chronologically later than f2, or if they're literally the same fence. Same fence? still slay, still true. 💅

⚠️ okay this part matters, do not skip it: both fences must be from the same context, because a seqno is not re-used across contexts. like, the seqnos only make sense inside one context, so comparing across contexts is giving chaos and it's not the move 😭

---

🦋 SEE ALSO 🦋

Kernel file ./include/linux/dma-fence.h, plus the whole friend group of related pages — go say hi 👋

• struct dma_fence(9)
• struct dma_fence_cb(9)
• struct dma_fence_ops(9)
• dma_fence_was_initialized(9)
• dma_fence_put(9)
• dma_fence_get(9)
• dma_fence_get_rcu(9)
• dma_fence_get_rcu_safe(9)
• dma_fence_spinlock(9)
• dma_fence_lock_irqsave(9)
• dma_fence_unlock_irqrestore(9)
• dma_fence_assert_held(9)
• Safe external access to driver provided object members(9)
• dma_fence_is_signaled_locked(9)
• dma_fence_is_signaled(9)
• __dma_fence_is_later(9)
• dma_fence_is_later(9)
• dma_fence_later(9)
• dma_fence_get_status_locked(9)
• dma_fence_set_error(9)
• dma_fence_timestamp(9)
• dma_fence_wait(9)
• dma_fence_is_array(9)
• dma_fence_is_chain(9)
• dma_fence_is_container(9)

---

and that's the whole page, bestie, you ate that 🍓

mwah, this one came from the ./include/linux corner of the kernel, dated October 2026, and yes she's filed under dma_fence_is_later_or_same(9) — go forth and compare fences responsibly 💜✨