xsk_tx_metadata_request(9)

✨ xsk_tx_metadata_request(9) ✨

okay so bestie, welcome to the kernel API manual (yes, the real one, xsk_tx_metadata_request(9)) — this page is short but it absolutely ate 💅

🌸 NAME 🌸

xsk_tx_metadata_request — literally the function that evaluates AF_XDP TX metadata at submission and then calls the appropriate xsk_tx_metadata_ops operation. no cap, that's the whole gig 🎀

🦋 SYNOPSIS 🦋

void xsk_tx_metadata_request (const struct xsk_buff_pool *pool , struct
xsk_tx_metadata **pmeta , const struct xsk_tx_metadata_ops *ops , void
*priv );

💖 ARGUMENTS 💖

• pool — pointer to the AF_XDP buffer pool. it's used to validate the metadata, so like… it's the vibe check for your metadata ✅
• pmeta — pointer to a pointer to the AF_XDP metadata area 👀 double pointer energy, she's iconic
• ops — pointer to struct xsk_tx_metadata_ops
• priv — pointer to the driver-private area 🙈 that's where the driver keeps its lil secrets

⭐ DESCRIPTION ⭐

so the networking device should call this function when it's preparing an AF_XDP egress packet. that's it. that's the assignment. main character behaviour honestly 👑

ngl, the "should be called" here is real — the device is the one that's supposed to hit this up when it's getting an egress packet ready 🫶

🌈 SEE ALSO 🌈

• Kernel file ./include/net/xdp_sock_drv.h
• xsk_buff_raw_get_ctx(9)

and that's the whole page bestie, go forth and validate that metadata 💜✨🎀

sign-off fr fr: this one lives in ./include/net, dated October 2026 — shoutout to the kernel API manual for keeping us fed 🧚‍♀️🍓