libie_ctlq_init(9)

📦 version 7.3.1, in nixpkgs unstable

💫 libie_ctlq_init — the main character of control queue setup 💫

okay so this is libie_ctlq_init(9), and it's living in the Kernel API Manual, section 9. bestie, this is the main initialization routine for all control queues and honestly? it ate. 🎀

🌸 SYNOPSIS 🌸

int libie_ctlq_init (struct libie_ctlq_ctx *ctx , const struct
libie_ctlq_create_info *qinfo , u32 numq );

✨ ARGUMENTS ✨

  • ctx — the libie CP context information. like, the whole vibe of your CP, packaged up. 🫶
  • qinfo — an array of structs containing info for each queue to be initialized. yes, an array — one entry per queue, no skipping. 🔥
  • numq — the number of queues to initialize. literally how many we're doing today. 💅

🦋 DESCRIPTION 🦋

This initializes the queue list and adds any number and any type of control queues. so flexible, so iconic. ✨

ngl, this is an all or nothing routine — if one of them fails, all previously allocated queues get destroyed. no half-finished setups here, it's giving clean slate or nothing. 😭

💀 important vibe check: any control queue send/receive functions are not softirq/NAPI safe, and therefore this API can be used in process context only. do not try it anywhere else, fr fr. 🙈

🌈 RETURN 🌈

  • 0 on success — slay 💖
  • -errno on failure — the sad path 😭

👑 SEE ALSO 👑

Kernel file ./drivers/net/ethernet/intel/libie/controlq.c — the source, the origin story, go read it 🧚

that's the whole bestie list, no cap — go click through all of them, they're all linked up and ready 💜

k that's the page!! source is ./drivers/net/ethernet/intel/l... and it's dated October 2026 — mwah, stan, bye 🍓💅🫶

📦 where this page comes from