libeth_xdp_xmit_fill_buf(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… libeth_xdp_xmit_fill_buf β€” NAME

okay so bestie, this is libeth_xdp_xmit_fill_buf from the Kernel API Manual and it's literally the internal helper to fill one XDP xmit &libeth_sqe πŸŽ€

internal means internal, babes β€” this is not the function you call from your driver, it's the one the library calls for you πŸ’…

✨ SYNOPSIS ✨

struct libeth_xdp_tx_desc libeth_xdp_xmit_fill_buf (struct libeth_xdp_tx_frame frm , u32 i , const struct libeth_xdpsq *sq , u64 priv );

like, she takes four things and gives you back a whole descriptor. main character energy fr fr πŸ‘‘


🫢 ARGUMENTS 🫢

  • frm β€” the XDP Tx frame, straight out of the bulk. that's her 🌸
  • i β€” the index on the HW queue. yes, the actual hardware queue, not a vibe 😭
  • sq β€” the XDPSQ abstraction for the queue. it's the const one, she's just visiting πŸ’œ
  • priv β€” private data. mind your business bestie πŸ™ˆ

πŸ’– RETURN πŸ’–

she hands you back an XDP Tx descriptor β€” with the mapped DMA and other info all bundled up, ready to pass to the driver callback. like a little care package but for your NIC πŸ“¦βœ¨


πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file: ./include/net/libeth/xdp.h β€” literally the whole lore lives there iykyk

and the full bestie roster, no cap, every single one:


and that's the whole page bestie, mwah πŸ’‹

this iconic little drop comes to you from ./include/net/libeth, dated October 2026, and it's still out here answering to the name libeth_xdp_xmit_fill_buf(9). slay πŸŽ€βœ¨

πŸ“¦ where this page comes from