ice_aq_add_vsi(9)
πΈ NAME πΈ
Okay so you pulled up ice_aq_add_vsi β and yes, the manual name is ice_aq_add_vsi(9), full Kernel API Manual energy. The original NAME section is basically the function name, a little dash, and then nothing, which is so mysterious of it, but we're here now. π«Ά
β¨ SYNOPSIS β¨
int ice_aq_add_vsi (struct ice_hw *hw , struct ice_vsi_ctx *vsi_ctx ,
struct ice_sq_cd *cd );
This returns an int, and those are the exact three arguments, no cap. π
π ARGUMENTS π
hwβ pointer to the HW struct. That's the hardware bestie you're handing over. πvsi_ctxβ pointer to a VSI context struct. It's the VSI context in question, periodt.cdβ pointer to command details structure orNULL. So it can be a real command-details pointer, or the classicNULLvibe. π¦
π DESCRIPTION π
Add a VSI context to the hardware β that's the whole mission, and it's tagged with 0x0210. Short, sweet, iconic. β¨
π¦ SEE ALSO π¦
First, the kernel file to know: ./drivers/net/ethernet/intel/ice/ice_switch.c. Then the whole related-function squad, all listed with their (9) energy, fr fr:
ice_init_def_sw_recp(9)ice_aq_get_sw_cfg(9)ice_aq_free_vsi(9)ice_aq_update_vsi(9)ice_is_vsi_valid(9)ice_get_hw_vsi_num(9)ice_get_vsi_ctx(9)ice_save_vsi_ctx(9)ice_clear_vsi_q_ctx(9)ice_clear_vsi_ctx(9)ice_clear_all_vsi_ctx(9)ice_add_vsi(9)ice_free_vsi(9)ice_update_vsi(9)ice_cfg_rdma_fltr(9)ice_aq_alloc_free_vsi_list(9)ice_aq_sw_rules(9)ice_aq_add_recipe(9)ice_aq_get_recipe(9)ice_update_recipe_lkup_idx(9)ice_aq_map_recipe_to_profile(9)ice_aq_get_recipe_to_profile(9)ice_init_chk_recipe_reuse_support(9)ice_alloc_recipe(9)ice_free_recipe_res(9)ice_release_recipe_res(9)ice_get_recp_to_prof_map(9)ice_get_recp_frm_fw(9)ice_fill_sw_info(9)ice_fill_eth_hdr(9)ice_fill_sw_rule(9)ice_add_marker_act(9)ice_create_vsi_list_map(9)ice_update_vsi_list_rule(9)ice_create_vsi_list_rule(9)ice_create_pkt_fwd_rule(9)ice_update_pkt_fwd_rule(9)ice_update_sw_rule_bridge_mode(9)ice_add_update_vsi_list(9)ice_find_rule_entry(9)ice_find_vsi_list_entry(9)ice_add_rule_internal(9)ice_remove_vsi_list_rule(9)ice_rem_update_vsi_list(9)ice_remove_rule_internal(9)ice_vlan_fltr_exist(9)ice_add_mac(9)ice_add_vlan_internal(9)ice_add_vlan(9)ice_add_eth_mac(9)ice_remove_eth_mac(9)ice_rem_sw_rule_info(9)ice_rem_adv_rule_info(9)ice_cfg_dflt_vsi(9)ice_vsi_uses_fltr(9)ice_check_if_dflt_vsi(9)ice_remove_mac(9)ice_remove_vlan(9)ice_add_entry_to_vsi_fltr_list(9)ice_add_to_vsi_fltr_list(9)ice_determine_promisc_mask(9)ice_remove_promisc(9)ice_clear_vsi_promisc(9)ice_set_vsi_promisc(9)ice_set_vlan_vsi_promisc(9)ice_remove_vsi_lkup_fltr(9)ice_remove_vsi_fltr(9)ice_alloc_res_cntr(9)ice_free_res_cntr(9)ice_share_res(9)ice_find_recp(9)ice_change_proto_id_to_dvm(9)ice_prot_type_to_id(9)ice_fill_valid_words(9)ice_fill_fv_word_index(9)ice_find_free_recp_res_idx(9)ice_calc_recp_cnt(9)ice_add_sw_recipe(9)ice_subscribe_recipe(9)ice_subscribable_recp_shared(9)ice_add_adv_recipe(9)ice_dummy_packet_add_vlan(9)ice_find_dummy_packet(9)ice_fill_adv_dummy_packet(9)ice_fill_adv_packet_tun(9)ice_fill_adv_packet_vlan(9)ice_find_adv_rule_entry(9)ice_adv_add_update_vsi_list(9)ice_add_adv_rule(9)ice_replay_vsi_fltr(9)ice_adv_rem_update_vsi_list(9)ice_rem_adv_rule(9)ice_rem_adv_rule_by_id(9)ice_replay_vsi_adv_rule(9)ice_replay_vsi_all_fltr(9)ice_rm_all_sw_replay_rule_info(9)
Cute sign-off, bestie: the source/version on this one is ./drivers/net/ethernet/intel/ice, and the date is October 2026 β the footer also had ice_aq_add_vsi(9) doing its little reprise, but we are not copying the whole footer line, we are simply acknowledging the vibe. Byeee! ππ«Άβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms