libie_ctlq_xn_send(9)

📦 version 7.3.1, in nixpkgs unstable

💌 libie_ctlq_xn_send(9) — bestie's guide to yeeting a control queue message

okay so this is a Kernel API Manual page, section 9 (iykyk, that's the kernel interfaces girlies), and we're talking about libie_ctlq_xn_send — the function that sends a control queue message and starts a whole transaction. main character energy fr. 🎀

✨ SYNOPSIS ✨

int libie_ctlq_xn_send (struct libie_ctlq_xn_send_params *params );

like, one arg, one int back, no cap. 💅

🌸 ARGUMENTS 🌸

  • params — the Xn send param information used for sending a control queue message. she's literally the blueprint for the send, everything hinges on her 🫶

🦋 DESCRIPTION 🦋

so basically you're sending a control queue message — think mailbox or config, those are the two vibes it covers. lowkey simple right?

here's the tea though 👑: based on whatever the params value says, the call can be completed synchronously or asynchronously. yes bestie, two different timelines, and it's params that decides which one you're living in. choose wisely. 😭

⭐ RETURN ⭐

  • 0 on success — slay, we ate 🍓
  • -errno on failure — not slay, go check your errno 💀

🔥 SEE ALSO 🔥

first up, the home turf — the kernel file this all lives in:

./drivers/net/ethernet/intel/libie/controlq.c

and now the whole friend group, everyone gets their flowers 💐:

also note the __ prefix on __libie_ctlq_xn_push_free(9) — that's the double-underscore "i'm the internal one" energy, don't mix her up with libie_ctlq_xn_push_free(9) 🙈

and that's the whole page, bestie!! source is ./drivers/net/ethernet/intel/l... (yes it's literally truncated like that, that's what the page says, don't come for me 😭) and it's dated October 2026 — future iconic behavior fr fr. mwah 💖🧚‍♀️🌷

📦 where this page comes from