xdp_reg_page_pool(9)

okay bestie, you’re looking at xdp_reg_page_pool(9) from the Kernel API Manual — yes, the manual name is folded in near the top, we move 💅✨

🌸 NAME 🌸

xdp_reg_page_pool — register &page_pool as a memory provider for XDP 💖

✨ SYNOPSIS ✨

int xdp_reg_page_pool (struct page_pool *pool );

🫶 ARGUMENTS 🫶

• pool — the page_pool to register 🫶

🌈 DESCRIPTION 🌈

okay so here’s the vibe: you can use this to register pools manually without connecting to any XDP RxQ info, so that the XDP layer will be aware of them. Then they can be attached to an RxQ info manually via xdp_rxq_info_attach_page_pool. literally the hand-off of all time ✨

🎀 RETURN 🎀

0 on success, -errno on error. periodt 💅

👀 SEE ALSO 👀

• Kernel file: ./net/core/xdp.c
• 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_timestamp(9)
• bpf_xdp_metadata_rx_hash(9)
• bpf_xdp_metadata_rx_vlan_tag(9)

okay that’s the whole page — source path ./net/core, dated October 2026, page xdp_reg_page_pool(9), mwah 💋🦋