libie_ctlq_send_clean(9)

📦 version 7.3.1, in nixpkgs unstable

💅 libie_ctlq_send_clean — the NAME bit ✨

okay so picture this: it's libie_ctlq_send_clean(9), from the Kernel API Manual, and she's here to clean up the send control queue message buffers. yes bestie, she does the tidying. we love a domestic icon 🧹🎀

✨ SYNOPSIS ✨

u32 libie_ctlq_send_clean (const struct libie_ctlq_clean_params *params
);

literally just one param and she returns a u32. lowkey elegant, no cap 💅

🫶 ARGUMENTS 🫶

  • params — the info she needs for handling of Tx completions. that's the vibe check she runs on incoming completions, bestie 💖

🌸 DESCRIPTION 🌸

so what she does is cleanup the send buffers for the given control queue. 🧚

now here's the tea: if force is set, she clears all the outstanding send messages — irrespective of their send status — and she keeps going until a zero-length message is encountered. and what is that zero-length message, you ask? it's either:

  • a message that's already been cleared, or
  • a VF reset message, which is always last. periodt. 🔥
warning bestie: Force should be used during deinit or reset. that's the only time she's supposed to go full scorched-earth mode, okay? don't be weird about it 💀

👑 RETURN 👑

the number of send buffers she cleaned. that's it, that's the number. she ate and left crumbs 🍓

🦋 SEE ALSO 🦋

the kernel file is right here, go be nosy: ./drivers/net/ethernet/intel/libie/controlq.c

and here's the whole friend group, all of them, nobody left out, i would never 🙈💜

and that's the whole page bestie!! she's sourced from ./drivers/net/ethernet/intel/l... (yeah the path is literally cut off like that in the footer, iconic of her honestly 😭), dated October 2026, and yes she's still living under the name libie_ctlq_send_clean(9) forever and ever, mwah 💖🎀✨

📦 where this page comes from