ice_flow_assoc_prof(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ice_flow_assoc_prof(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” yes, the actual kernel one, and yes, we're gonna get through it together 🫢


✨ NAME ✨

ice_flow_assoc_prof β€” the girl whose whole job is associating a VSI with a flow profile. that's it. that's the vibe. πŸ’«


🌸 SYNOPSIS 🌸

int ice_flow_assoc_prof (struct ice_hw *hw , enum ice_block blk , struct
ice_flow_prof *prof , u16 vsi_handle );

like, four things go in, an int comes out, she's iconic πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • hw β€” pointer to the hardware structure. the hardware. the main character. πŸ–₯️✨
  • blk β€” classification stage, as an enum ice_block. it's giving "which chapter of the story are we in" ngl πŸ“–
  • prof β€” pointer to flow profile. the profile in question. she's a pointer, she's real πŸ’œ
  • vsi_handle β€” software VSI handle, a u16. lowercase, understated, doing the work 🌸

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the thing β€” there is an assumption happening here, and bestie you cannot skip it:

the caller has acquired the lock to the profile list and the software VSI handle has been validated.

lowkey that's the entire description and it's non-negotiable, fr fr. you show up with the lock held and the vsi_handle already validated, or you don't show up at all πŸ˜€πŸ”’


⭐ SEE ALSO ⭐

the kernel file lives right here: ./drivers/net/ethernet/intel/ice/ice_flow.c β€” go read her, she's long but she ate πŸ“

and now the extended friend group, in order, no one left out, periodt:

like, the whole ice_flow + ice_rss friend group pulled up to the group chat at once πŸ”₯πŸ‘‘


and that's the whole page, no notes πŸ’– this lil beauty comes to you straight from ./drivers/net/ethernet/intel/ice and she's stamped October 2026 β€” go forth, hold that lock, validate that handle, slay πŸ§šβ€β™€οΈπŸŒˆ

πŸ“¦ where this page comes from