ice_update_vsi_list_rule(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

ice_update_vsi_list_rule(9) is the function, bestie, and this page is straight from the Kernel API Manual. It’s giving β€œupdate the VSI list rule” energy, and we’re obsessed. πŸ’–


✨ SYNOPSIS ✨

int ice_update_vsi_list_rule (struct ice_hw *hw , u16 *vsi_handle_arr ,
       u16 num_vsi , u16 vsi_list_id , bool remove , enum ice_adminq_opc opc ,
       enum ice_sw_lkup_type lkup_type );

πŸ¦‹ ARGUMENTS πŸ¦‹

Okay so this call takes these cuties:

  • hw β€” pointer to the hardware structure. Hardware bestie, essential. πŸ’»
  • vsi_handle_arr β€” array of VSI handles to form a VSI list. It’s literally the squad list. 🫢
  • num_vsi β€” number of VSI handles in the array. Counting is caring, bestie.
  • vsi_list_id β€” VSI list ID generated as part of allocate resource. Resource allocation ate, no cap.
  • remove β€” Boolean value to indicate if this is a remove action. Yes, it’s the β€œare we removing?” boolean.
  • opc β€” switch rules population command type β€” pass in the command opcode. You gotta pass it in, okay?
  • lkup_type β€” lookup type of the filter. The filter’s whole lookup vibe. 🌈

🌸 DESCRIPTION 🌸

Bestie, the main character moment is this: call AQ command to add a new switch rule or update existing switch rule using the given VSI list ID. That’s the whole plot. It’s the add/update switch-rule situation, and it’s using the VSI list ID you gave it. Slay. πŸ”₯


πŸ’… SEE ALSO πŸ’…

Kernel file first, no cap: ./drivers/net/ethernet/intel/ice/ice_switch.c.

Then the whole function family reunion, in the order the page gives them:


Okay that’s the whole page, bestie. Source/version: ./drivers/net/ethernet/intel/ice; date: October 2026. Mwah πŸ’– periodt. 🫢

πŸ“¦ where this page comes from