dma_fence_array_init(9)

💅 dma_fence_array_init(9) — Kernel API Manual, bestie edition ✨

okay so this is dma_fence_array_init, from the Kernel API Manual, and it's literally the glow-up helper for preallocated fence arrays 🎀 no cap.

---

✨ NAME ✨

dma_fence_array_init — Init a custom fence array 🦋

---

🌸 SYNOPSIS 🌸

void dma_fence_array_init (struct dma_fence_array *array , int
num_fences , struct dma_fence **fences , u64 context , unsigned seqno );

it's giving void, it takes five args, and yes bestie it is exactly that signature, copy it verbatim, do not freestyle 🙈

---

💖 ARGUMENTS 💖

• array [in] — the dma fence array you're arming up 👑 this is the main character.
• num_fences [in] — how many fences you're adding into the array, count them fr fr 🔥
• fences [in] — the array that contains the fences 🌈
• context [in] — the fence context to use, u64, keep it 💜
• seqno [in] — the sequence number to use, unsigned, slay 💅

---

🧚 DESCRIPTION 🧚

okay so here's the tea ☕: this is the implementation of dma_fence_array_create without allocation. literally the same energy, zero malloc drama 💀

it's useful to init a preallocated dma fence array, specifically when you're in the path of reclaim or dma fence signaling. so like, when you can't go allocating stuff, this is your girl 🫶

lowkey important: no allocation happens here. that's the whole point. that's the vibe check it passes ✨

---

🦋 SEE ALSO 🦋

• kernel file ./drivers/dma-buf/dma-fence-array.c 📁
• dma_fence_array_alloc(9)
• dma_fence_array_create(9)
• dma_fence_match_context(9)

go read those next, iykyk 💖

---

and that's the whole page, bestie ✨ this cutie lives in ./drivers/dma-buf, it's dated October 2026, and it's page dma_fence_array_init(9) of the Kernel API Manual — go forth and arm those preallocated arrays, periodt 💅🎀🌸