ENUM NETDEV_XDP_RX_METADATA(9)

🌸 enum netdev_xdp_rx_metadata(9) 🌸

okay bestie so this one's from the Kernel API Manual — it's the enum that's basically a vibe check for what your NIC can actually do with XDP receive metadata 💅 like, which little extras come free with your packets. no cap, it's tiny, but it's the whole group chat of RX metadata capabilities.

---

✨ NAME ✨

enum netdev_xdp_rx_metadata — the enum of "can my device even do this tho" for XDP receive metadata 🎀

---

✨ SYNOPSIS ✨

enum netdev_xdp_rx_metadata {
    NETDEV_XDP_RX_METADATA_TIMESTAMP ,
    NETDEV_XDP_RX_METADATA_HASH ,
    NETDEV_XDP_RX_METADATA_VLAN_TAG

};

---

🫶 DESCRIPTION 🫶

there's no big essay here, bestie — this whole page is just the enum and the three constants in it. they're flags, and each one means your device can surface that specific piece of RX metadata. that's the entire lore. iykyk 🌈

---

🎀 Constants 🎀

• NETDEV_XDP_RX_METADATA_TIMESTAMP — your device is capable of exposing the receive HW timestamp via bpf_xdp_metadata_rx_timestamp. ⏰✨ literally the clock info, handed to you.
• NETDEV_XDP_RX_METADATA_HASH — your device is capable of exposing the receive packet hash via bpf_xdp_metadata_rx_hash. 🍓 the hash of the packet, right there for the taking.
• NETDEV_XDP_RX_METADATA_VLAN_TAG — your device is capable of exposing the receive packet VLAN tag via bpf_xdp_metadata_rx_vlan_tag. 🏷️ the VLAN tag, exposed and iconic.

heads up: each of these is a capability claim about the device, fr fr — it's saying the device can do it, not that it's doing it rn.

---

👀 SEE ALSO 👀

• Kernel file ./tools/include/uapi/linux/netdev.h — the source of truth, go read it bestie 📖
• enum netdev_xdp_act(9)
• enum netdev_xsk_flags(9)

---

and that's the page, no notes. 💖 sign-off time: this one lives in ./tools/include/uapi/linux, dated October 2026, and yes it's enum netdev_xdp_rx_metadata(9) — periodt. 🦋👑