idpf_vport_get_q_reg(9)

📦 version 7.3.1, in nixpkgs unstable

🌈 idpf_vport_get_q_reg(9) 🌈

okay so you opened the idpf_vport_get_q_reg(9) page and you're in the Kernel API Manual bestie, welcome, let's get you fluent 💅 this one is short and sweet, no cap — it's a little helper that goes digging through queue register chunk info and pulls out the offsets.

✨ NAME ✨

idpf_vport_get_q_reg — Get the queue registers for the vport 🎀

🦋 SYNOPSIS 🦋

int idpf_vport_get_q_reg (u32 *reg_vals , int num_regs , u32 q_type ,
       struct idpf_queue_id_reg_info *chunks );

💖 ARGUMENTS 💖

  • reg_vals — the register values that need to be set, i.e. the array you're handing over so it can get filled ✨
  • num_regs — how many you expect to fill 🫶 like, your hopes and dreams in integer form
  • q_type — the queue model 🌸
  • chunks — the queue regs that came in over the mailbox 📬

🎀 DESCRIPTION 🎀

So what does it actually do? It parses the queue register offsets out of the queue register chunk information — for a specific queue type, q_type — and stores them into the array you passed in as an argument (reg_vals, that one). Then it returns the actual number of queue registers that got filled 👑

tl;dr: you bring the array, it brings the offsets, and the count you get back is the real count, not your num_regs wish 😭

⭐ SEE ALSO ⭐

kernel file ./drivers/net/ethernet/intel/idpf/idpf_virtchnl.c — that's the main character, go read it 🧚

and the whole friend group, in order:

💀 friendly reminder bestie: the count you get back is the actual filled count, so don't go assuming it's always your num_regs, okay? vibe check your array length 🙈

and that's the whole page, periodt 🫶 this little gem lives under ./drivers/net/ethernet/intel/idpf, dated October 2026, and it's part of the Kernel API Manual — go off, you're basically a kernel dev now 👑💖

📦 where this page comes from