xdp_rxq_inf...ch_page_pool(9)
π xdp_rxq_info_attach_page_pool β the Kernel API Manual edit π
okay bestie, so we're in the Kernel API Manual rn and the star of the show is xdp_rxq_info_attach_page_pool (the header truncates it all cute as xdp_rxq_inf...ch_page_pool(9), iykyk). it's literally the function that hooks a registered pool up to your RxQ info. slay.
β¨ NAME β¨
xdp_rxq_info_attach_page_pool β attach registered pool to RxQ info π«Ά
πΈ SYNOPSIS πΈ
void xdp_rxq_info_attach_page_pool (struct xdp_rxq_info *xdp_rxq , const
struct page_pool *pool );
like, it returns void β it does the thing and dips, no return value era π
π¦ ARGUMENTS π¦
xdp_rxqβ the XDP RxQ info you're attaching the pool to πpoolβ the pool to attach, bestie. that's the one. β¨
π₯ DESCRIPTION π₯
okay so here's the tea β β if the pool was registered manually, you must call this function instead of xdp_rxq_info_reg_mem_model to connect it to the RxQ info. like, not optional, not a vibe suggestion β must. periodt. π
not me stressing this but fr fr: manual registration means this is the connector, not xdp_rxq_info_reg_mem_model. don't mix them up π
π SEE ALSO π
- the kernel file
./net/core/xdp.cβ that's the home base π xdp_reg_page_pool(9)xdp_unreg_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)
like, read them all. they're all iconic in their own way π
and that's the whole page, bestie π sign-off time: this one's from ./net/core, dated October 2026, and yes it's the same xdp_rxq_inf...ch_page_pool(9) in the corner β we stay consistent πβ¨π¦
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms