ice_get_xp_from_qid(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ice_get_xp_from_qid(9) β€” the Kernel API Manual glow-up ✨

okay so bestie, welcome to ice_get_xp_from_qid(9), a genuine little function from the Kernel API Manual and honestly? it's giving "small but mighty" πŸ’–


🌸 NAME 🌸

ice_get_xp_from_qid β€” get ZC XSK buffer pool bound to a queue ID

like literally, that's the whole job. it goes and finds the zero-copy XSK buffer pool that's attached to a particular queue ID πŸŽ€


✨ SYNOPSIS ✨

struct xsk_buff_pool * ice_get_xp_from_qid (struct ice_vsi *vsi , u16
qid );

she takes two things and she hands you back a struct xsk_buff_pool *. no cap 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • vsi β€” pointer to VSI. that's your struct ice_vsi *, the main character of this whole operation πŸ‘‘
  • qid β€” index of a queue to look at XSK buff pool presence. you're basically asking "hey, is there an XSK buff pool hanging out at this queue index?" πŸ™ˆ

πŸ’œ RETURN πŸ’œ

A pointer to xsk_buff_pool structure if there is a buffer pool attached and configured as zero-copy. otherwise? NULL. that's it, that's the vibe check πŸ’€

ngl, that "and configured as zero-copy" part is doing heavy lifting β€” it's not just "is there a pool", it's "is there a pool that's set up for zero-copy". both boxes gotta be ticked, fr fr βœ…

🌈 SEE ALSO 🌈

first up, the kernel file itself, go peek:

  • Kernel file ./drivers/net/ethernet/intel/ice/ice.h

and then the whole friend group, in order, because we do not skip anyone at this table πŸ“:

lowkey an iconic lineup πŸ’…


and that's the page!! sourced straight from ./drivers/net/ethernet/intel/ice, dated October 2026, and yes the manual name is ice_get_xp_from_qid(9) in case you forgot already 😭 go read your XSK pools bestie, ily, bye πŸ§šβ€β™€οΈπŸ’–

πŸ“¦ where this page comes from