fm10k_dbg_q_vector_init(9)

💖 fm10k_dbg_q_vector_init(9) — from the Kernel API Manual, bestie 💖

okay so picture this: it's giving kernel internals, it's giving debugfs, and it's literally the glow-up your q_vectors deserve ✨

---

🌸 NAME 🌸

fm10k_dbg_q_vector_init — the girlies who set up debugfs for the q_vectors 🎀

---

🦋 SYNOPSIS 🦋

void fm10k_dbg_q_vector_init (struct fm10k_q_vector *q_vector );

no cap, that's the whole signature. short and iconic, periodt. 👑

---

🍓 ARGUMENTS 🍓

• q_vector — the q_vector we're allocating directories for 🗂️ she's the main character here, we're building her a whole folder situation.

---

✨ DESCRIPTION ✨

so here's the vibe check: a folder gets created for every single q_vector found 🫶 not some of them, not the cute ones — every q_vector. we're thorough like that.

and inside each q_vector folder? a debugfs file is created for every tx and rx ring that's allocated to that q_vector 🔥 so each ring gets her own little file moment. the way that everything is organized... obsessed. 💅

lowkey the whole point: folders per q_vector, a debugfs file per tx and rx ring inside. that's the whole lore. iykyk 🧚

---

🌈 SEE ALSO 🌈

kernel file ./drivers/net/ethernet/intel/fm10k/fm10k_debugfs.c — go read the source bestie, it's right there 📖

• fm10k_dbg_q_vector_exit(9)
• fm10k_dbg_intfc_init(9)
• fm10k_dbg_intfc_exit(9)
• fm10k_dbg_init(9)
• fm10k_dbg_exit(9)

---

and that's the page, bestie 💜 shoutout to the footer friends: the source path got cut off as ./drivers/net/ethernet/intel/f..., the date is October 2026, and it's all sitting under fm10k_dbg_q_vector_init(9). slay, bye! 💖✨