ice_vc_get_stats_msg(9)
π ice_vc_get_stats_msg(9) β the group chat edition π
Okay bestie, buckle up, we're reading the Kernel API Manual page for ice_vc_get_stats_msg β yes that's the manual name, it's a whole (9) situation, kernel-internals vibes only, iykyk β¨
πΈ NAME πΈ
ice_vc_get_stats_msg β and the manpage just... leaves the description blank π literally nothing after the dash. Not me side-eyeing the doc generator fr fr. Anyway, the name is the name, periodt π
π¦ SYNOPSIS π¦
int ice_vc_get_stats_msg (struct ice_vf *vf , u8 *msg );
That's the whole signature, no cap. int goes in, int comes out, two args in the middle π«Ά
β¨ ARGUMENTS β¨
vfβ pointer to the VF info π (the virtual function's whole little profile, basically)msgβ pointer to the msg buffer π (the actual message payload living in memory)
Both are pointers, both matter, don't lose either one π§
π DESCRIPTION π
So ice_vc_get_stats_msg is called from the VF to get VSI stats β that's the entire description, and honestly? Iconic brevity. The virtual function hits up this function when it wants the VSI statistics, and that's the tea β The docs are giving minimalist main character energy and I respect it π
Heads up: the original page says literally nothing more than that, so I'm not gonna invent extra lore for you β I refuse to make up technical claims, that's not the vibe πΈ
π₯ SEE ALSO π₯
The mother of all see-also lists, bestie, we are FEASTING tonight π
Kernel file ./drivers/net/ethernet/intel/ice/virt/virtchnl.c
And the iconically long cast of characters, all in (9), all here, all accounted for π
:
ice_vc_vf_broadcast(9),ice_set_pfe_link(9),ice_vc_notify_vf_link_state(9),ice_vc_notify_link_state(9),ice_vc_notify_reset(9),ice_vc_send_msg_to_vf(9),ice_vc_get_ver_msg(9),ice_vc_get_vlan_caps(9),ice_vc_get_vf_res_msg(9),ice_vc_reset_vf_msg(9),ice_vc_isvalid_vsi_id(9)ice_vc_get_qos_caps(9),ice_vc_cfg_promiscuous_mode_msg(9),ice_can_vf_change_mac(9),ice_vc_ether_addr_type(9),ice_is_vc_addr_legacy(9),ice_is_vc_addr_primary(9),ice_vfhw_mac_add(9),ice_is_mc_lldp_eth_addr(9),ice_vc_can_add_mac(9),ice_vc_add_mac_addr(9),ice_is_legacy_umac_expired(9),ice_update_legacy_cached_mac(9),ice_vfhw_mac_del(9),ice_vc_del_mac_addr(9)ice_vc_handle_mac_addr_msg(9),ice_vc_add_mac_addr_msg(9),ice_vc_del_mac_addr_msg(9)ice_vf_vlan_offload_ena(9),ice_is_vlan_promisc_allowed(9),ice_vf_ena_vlan_promisc(9),ice_vf_dis_vlan_promisc(9),ice_vf_has_max_vlans(9),ice_vc_process_vlan_msg(9),ice_vc_add_vlan_msg(9),ice_vc_remove_vlan_msg(9),ice_vsi_is_rxq_crc_strip_dis(9),ice_vc_ena_vlan_stripping(9),ice_vc_dis_vlan_stripping(9),ice_vc_query_rxdid(9),ice_vf_init_vlan_stripping(9),ice_vf_outer_vlan_not_allowed(9)ice_vc_set_dvm_caps(9),ice_vc_set_svm_caps(9),ice_vc_get_offload_vlan_v2_caps(9),ice_vc_validate_vlan_tpid(9),ice_vc_is_valid_vlan(9),ice_vc_validate_vlan_filter_list(9),ice_vc_to_vlan(9),ice_vc_vlan_action(9),ice_vc_del_vlans(9),ice_vc_remove_vlan_v2_msg(9),ice_vc_add_vlans(9),ice_vc_validate_add_vlan_filter_list(9),ice_vc_add_vlan_v2_msg(9),ice_vc_valid_vlan_setting(9),ice_vc_valid_vlan_setting_msg(9),ice_vc_get_tpid(9),ice_vc_ena_vlan_offload(9)ice_vc_ena_vlan_stripping_v2_msg(9),ice_vc_dis_vlan_stripping_v2_msg(9),ice_vc_ena_vlan_insertion_v2_msg(9),ice_vc_dis_vlan_insertion_v2_msg(9)ice_virtchnl_set_dflt_ops(9),ice_vc_repr_add_mac(9),ice_vc_repr_del_mac(9),ice_virtchnl_set_repr_ops(9),ice_is_malicious_vf(9),ice_vc_process_vf_msg(9)
That's 69 cross-references and yes I counted, we do not skip a single one in this house π β¨
And that's the whole page, bestie! π Cute little sign-off time: this came from source/version ./drivers/net/ethernet/intel/i... (the original footer truncates it with a ..., so that's exactly what we're giving you, no edits π) and it's dated October 2026, under the title ice_vc_get_stats_msg(9). Slay, go read your stats, you've earned it π«Άππ
π¦ 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