STRUCT LIBIE_CTLQ_XN_REL_TX_CTX(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct libie_ctlq_xn_rel_tx_ctx(9) πŸ’–

okay bestie, welcome to the Kernel API Manual moment for struct libie_ctlq_xn_rel_tx_ctx(9) β€” it’s giving β€œsmall struct, very specific job,” and honestly that’s iconic. This one is the context needed to release an xn Tx message. No cap, that’s the whole point. πŸŽ€


✨ NAME ✨

struct libie_ctlq_xn_rel_tx_ctx β€” context needed to release xn Tx message.

Like, it’s the little bundle of context you need when you’re doing the release-xn-Tx-message thing. Main character energy for a very niche task, and we respect it. πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

here’s the exact shape, bestie β€” do not freestyle it:

struct libie_ctlq_xn_rel_tx_ctx {
    struct device *dev;
    void (*rel_tx_buf)(const void *buf_va);
};

πŸ¦‹ Members πŸ¦‹

  • dev β€” device for which DMA was mapped. That’s the device this whole situation is tied to, fr fr. 🫢
  • rel_tx_buf β€” freeing function for non-small buffers. yes, β€œnon-small buffers” specifically β€” that’s the vibe, keep it exact. πŸ’–

🌈 SEE ALSO 🌈

Kernel file to peek at: ./drivers/net/ethernet/intel/libie/controlq.c πŸ‘‘

and the whole squad of (9) references, in order, no skips:


okay bye bestie 🫢 β€” source/version: ./drivers/net/ethernet/intel/l... Β· date: October 2026 Β· page: struct libi...n_rel_tx_ctx(9) πŸ’…

πŸ“¦ where this page comes from