xdp_rxq_inf...ch_page_pool(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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 πŸ’œ

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