octep_vf_oq...ring_buffers(9)

💅 octep_vf_oq_fill_ring_buffers(9) 💅

okay bestie, welcome to the Kernel API Manual — yes, that's the actual manual name, we're in the kernel docs now, put your hair up 🎀

---

✨ NAME ✨

octep_vf_oq_fill_ring_buffers — fills up the initial receive buffers for the Rx ring 🦋

like, it stocks the shelves before the party starts, no cap.

---

🌸 SYNOPSIS 🌸

int octep_vf_oq_fill_ring_buffers(struct octep_vf_oq *oq);

that's it. one function, one argument, very demure, very mindful 💅

---

🎀 ARGUMENTS 🎀

• oq — the Octeon Rx queue data structure 💖 the main character of this whole situation, honestly.

---

🔥 RETURN 🔥

• 0 — slay, it successfully filled receive buffers for all descriptors. every single one. iconic behavior ✨
• -ENOMEM — the flop era 😭 it failed to allocate a buffer, or it failed to map for DMA.

so yeah — if you get -ENOMEM back, bestie, something didn't get its memory or its DMA mapping, and the fill did not complete. fr fr.

---

🫶 SEE ALSO 🫶

the source lives right here in the kernel file:

./drivers/net/ethernet/marvell/octeon_ep_vf/octep_vf_rx.c

and here's the whole friend group 💜 go say hi:

• octep_vf_oq_refill(9)
• octep_vf_setup_oq(9)
• octep_vf_oq_free_ring_buffers(9)
• octep_vf_free_oq(9)
• octep_vf_setup_oqs(9)
• octep_vf_oq_dbell_init(9)
• octep_vf_free_oqs(9)
• octep_vf_oq_check_hw_for_pkts(9)
• __octep_vf_oq_process_rx(9)
• octep_vf_oq_process_rx(9)

---

and that's the whole page, bestie 💫 source path <lavender>./drivers/net/ethernet/marvell...</lavender>, dated October 2026, and it's filed under the octep_vf_oq...ring_buffers(9) header 🎀 love that for us. go fill those ring buffers, mwah 🍓