xsk_tx_metadata_complete(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

hey bestie πŸ’… welcome to xsk_tx_metadata_complete(9) from the Kernel API Manual β€” this page is lowkey iconic, and it's giving β€œAF_XDP TX metadata completion, but make it cute” ✨

🌸 NAME 🌸

xsk_tx_metadata_complete β€” evaluates AF_XDP TX metadata at completion and calls the appropriate xsk_tx_metadata_ops operation. That's the whole vibe, no cap πŸ’–

✨ SYNOPSIS ✨

void xsk_tx_metadata_complete (struct xsk_tx_metadata_compl *compl ,
       const struct xsk_tx_metadata_ops *ops , void *priv );

That's the signature, bestie β€” copy it exactly, periodt 🫢

πŸŽ€ ARGUMENTS πŸŽ€

  • compl β€” pointer to completion metadata produced from xsk_tx_metadata_to_compl
  • ops β€” pointer to struct xsk_tx_metadata_ops
  • priv β€” pointer to driver-private aread (yep, aread, the page said what it said πŸ™ˆ)

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so this function should be called by the networking device upon AF_XDP egress completion. It evaluates AF_XDP TX metadata at completion and calls the appropriate xsk_tx_metadata_ops operation β€” main character energy for your AF_XDP TX completion moment πŸ’…

πŸ’– SEE ALSO πŸ’–


And for the cute sign-off: source/version is ./include/net, date is October 2026, and the manual is still xsk_tx_metadata_complete(9) β€” bye bestie, go complete that TX metadata πŸ«ΆπŸ’–βœ¨

πŸ“¦ where this page comes from