__octep_vf_oq_process_rx(9)

📦 version 7.3.1, in nixpkgs unstable

💖 __octep_vf_oq_process_rx — the Kernel API Manual glow-up 🎀

okay so bestie, welcome to the Kernel API Manual page for __octep_vf_oq_process_rx and honestly? it's giving "small function, big job" energy. she processes the hardware Rx queue and pushes packets up to the stack. no cap. 🦋

✨ NAME ✨

__octep_vf_oq_process_rx — literally just: process hardware Rx queue and push to stack. that's the whole vibe. 💅

🌸 SYNOPSIS 🌸

int __octep_vf_oq_process_rx (struct octep_vf_device *oct , struct
octep_vf_oq *oq , u16 pkts_to_process );

like yes she takes three arguments and returns an int, main character behavior fr fr 😭

🫶 ARGUMENTS 🫶

  • oct — the Octeon device private data structure. your device's whole personality lives in here 💜
  • oq — the Octeon Rx queue data structure. this is the queue we're serving, she's the star of the show ⭐
  • pkts_to_process — number of packets to be processed. it's a u16, so know your limits bestie 🙈

👑 DESCRIPTION 👑

so what she does is process the new packets in the Rx queue 🔥. and here's the tea: packets that are larger than a single Rx buffer arrive in consecutive descriptors, okay? so they get split up across multiple descriptors.

⚠️ important detail, don't skip this: the count returned by the API only accounts for full packets, not fragments. so if you're out here counting descriptors thinking that's the packet count... that's not the vibe. the fragments don't get counted, periodt. 💀

🌈 RETURN 🌈

the number of packets processed and pushed to stack. that's it, that's the return. simple, iconic, slay ✨

🌟 SEE ALSO 🌟

kernel file: ./drivers/net/ethernet/marvell/octeon_ep_vf/octep_vf_rx.c

and the whole friend group 🫶:

and that's the page bestie!! 🧚 source: ./drivers/net/ethernet/marvell... 💖 dated October 2026 — go process some queues, you've got this, iykyk 🌸💅🎀

📦 where this page comes from