ice_flow_rem_vsi_prof(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ice_flow_rem_vsi_prof πŸ’…

okay so bestie, welcome to the ice_flow_rem_vsi_prof(9) page β€” that's section 9 of the Kernel API Manual, and yes we're doing kernel internals today, hydration is important 🫢


✨ NAME ✨

ice_flow_rem_vsi_prof β€” the "breakup" function πŸ’” where a VSI gets removed from a flow profile. it's giving "no longer associated, we don't know each other" energy, and honestly? iconic.


🌸 SYNOPSIS 🌸

int ice_flow_rem_vsi_prof (struct ice_hw *hw , u16 vsi_handle , u64
prof_id );

literally just three args and an int return, she's low maintenance πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • hw β€” pointer to the hardware structure. your main character struct, the one that knows things about the actual silicon πŸ”₯
  • vsi_handle β€” the software VSI handle. think of it as the vibe check ID for the VSI you're trying to unlink ✨
  • prof_id β€” a unique ID that identifies this particular flow profile. no cap, this is how we know which profile we're talking about πŸ‘‘

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea, bestie πŸ“: this function removes the flow entries associated to the input vsi_handle, and it disassociates the VSI from the flow profile. that's it, that's the whole vibe.

🧚 to be clear β€” it's both things at once: the flow entries tied to that VSI handle go bye-bye, and the VSI stops being associated with the flow profile. two-for-one, we love a multitasker πŸ’œ

🌈 SEE ALSO 🌈

if you're obsessed with this whole flow/RSS situation (and honestly, same), the kernel file lives right here:

./drivers/net/ethernet/intel/ice/ice_flow.c

and here's the whole friend group, zero skips, all of them πŸ”₯:

iykyk 😭 that's a lot of besties.


✨ mwah, that's a wrap ✨ this page lives under ./drivers/net/ethernet/intel/ice, dated October 2026, and it's ice_flow_rem_vsi_prof(9) forever and always πŸ’–πŸŽ€πŸ‘‘

πŸ“¦ where this page comes from