bpf_xdp_met...rx_timestamp(9)

✨ NAME ✨

okay so welcome to the Kernel API Manual page for bpf_xdp_met...rx_timestamp(9) — yes bestie, this is the one about bpf_xdp_metadata_rx_timestamp, and its whole job is: Read XDP frame RX timestamp. 💖 no cap, that's the vibe.

---

🫶 SYNOPSIS 🫶

no thoughts, just the exact signature — copy it character-for-character because code is sacred:

__bpf_kfunc int bpf_xdp_metadata_rx_timestamp (const struct xdp_md *ctx
, u64 *timestamp );

---

💅 ARGUMENTS 💅

• ctx — XDP context pointer. it's the XDP context pointer, main character energy 🫶
• timestamp — Return value pointer. literally the return value pointer, that's the whole description ✨

---

🎀 RETURN 🎀

• Returns 0 on success or -errno on error. 💖
• -EOPNOTSUPP : means device driver does not implement kfunc
• -ENODATA : means no RX-timestamp available for this frame

bestie, those error codes are important: -EOPNOTSUPP means the device driver does not implement kfunc, and -ENODATA means there is no RX-timestamp available for this frame. 😭✨

---

🌈 SEE ALSO 🌈

the cross-references are giving linked lore, so here's the whole set:

• Kernel file ./net/core/xdp.c
  • xdp_reg_page_pool(9)
  • xdp_unreg_page_pool(9)
  • xdp_rxq_info_attach_page_pool(9)
  • xdp_return_frag(9)
  • xdp_build_skb_from_buff(9)
  • xdp_copy_frags_from_zc(9)
  • xdp_build_skb_from_zc(9)
  • bpf_xdp_metadata_rx_hash(9)
  • bpf_xdp_metadata_rx_vlan_tag(9)

---

and that's the whole page, bestie 🫶 signing off from ./net/core, dated October 2026, for bpf_xdp_met...rx_timestamp(9). slay 💅✨