libeth_tx_complete_any(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… libeth_tx_complete_any(9) β€” like, the Kernel API Manual page you actually wanna read πŸŽ€

okay bestie, so this is a page from the Kernel API Manual and it's genuinely one of the shorter ones β€” but it's important, so stay with me ✨


🌸 NAME 🌸

libeth_tx_complete_any β€” the girl whose whole job is perform Tx completion for one SQE of any type πŸ’… no cap, that's literally it.


πŸ¦‹ SYNOPSIS πŸ¦‹

void libeth_tx_complete_any (struct libeth_sqe *sqe , struct
       libeth_cq_pp *cp );

like, look at her. two pointers, no return value. main character energy fr 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • sqe β€” the Tx buffer to complete, bestie. this is the one getting finished up ✨
  • cp β€” the polling params. that's what she's working with, okay? πŸ™ˆ

⭐ DESCRIPTION ⭐

so here's the vibe: this function can be used to complete both regular and XDP SQEs, for example when destroying queues. iconic, versatile, does both πŸ’–

but listen β€” When libeth_xdp is not loaded, XDPSQEs won't be handled. so like… if you didn't load the thing, don't expect the thing. 😭 that's the whole caveat, no cap.

🌈 SEE ALSO 🌈

  • Kernel file ./drivers/net/ethernet/intel/libeth/tx.c β€” go read the source, iykyk πŸ‘‘

that's the whole page babes, short and sweet πŸ“ and for the cute sign-off: this one's stamped October 2026, version/source line being that truncated ./drivers/net/ethernet/intel/l... bit β€” so like, yeah, that's the footer, we love a mysterious abbreviation πŸ’œβœ¨

πŸ“¦ where this page comes from