ice_vf_rebui...tor_node_cfg(9)
π ice_vf_rebuild_aggregator_node_cfg β the Kernel API Manual, bestie edition π
okay so real talk, this is a page from the Kernel API Manual and the function name is so long it got cut off in the header (ice_vf_rebui...tor_node_cfg(9)) β like, the manpage itself needed a trim π. Anyway, we're talking about the Intel ice driver here, and this one's a little cutie pie. Let's go β¨
πΈ NAME πΈ
ice_vf_rebuild_aggregator_node_cfg β rebuild aggregator node config
That's it. That's the whole vibe. It rebuilds the aggregator node config. Iconic, honestly π«Ά
β¨ SYNOPSIS β¨
void ice_vf_rebuild_aggregator_node_cfg (struct ice_vsi *vsi );
returns void, so likeβ¦ it does its thing and it does not want to talk about it. no return value, no drama, no cap π
π¦ ARGUMENTS π¦
vsiβ Pointer to VSI. bestie it's literally just a pointer, that's the whole argument, we love a low-maintenance parameter π
π DESCRIPTION π
okay so here's what's happening, and it's actually lowkey elegant:
This function moves the VSI into the corresponding scheduler aggregator node β and it does that based on the cached value of "aggregator node info" per VSI. so it's not like, recalculating anything from scratch, it's just going off the info it already saved. main character energy: knows what it wants, doesn't overthink π β¨
the way that it moves the VSI, not creates or destroys anything β just relocates it to where it belongs. slay π¦
π SEE ALSO π
the kernel file, first of all:
./drivers/net/ethernet/intel/ice/ice_vf_lib.c
and then, bestie, buckle up, because this is a long list of friends. every single one of them, in order, no skips, no cuts π€:
ice_get_vf_by_id(9)ice_release_vf(9)ice_put_vf(9)ice_has_vfs(9)ice_get_num_vfs(9)ice_get_vf_vsi(9)ice_is_vf_disabled(9)ice_wait_on_vf_reset(9)ice_check_vf_ready_for_cfg(9)ice_trigger_vf_reset(9)ice_vf_pre_vsi_rebuild(9)ice_vf_reconfig_vsi(9)ice_vf_rebuild_vsi(9)ice_vf_rebuild_host_vlan_cfg(9)ice_vf_rebuild_host_tx_rate_cfg(9)ice_vf_set_host_trust_cfg(9)ice_vf_rebuild_host_mac_cfg(9)ice_vf_rebuild_host_cfg(9)ice_set_vf_state_qs_dis(9)ice_vf_set_initialized(9)ice_vf_post_vsi_rebuild(9)ice_is_any_vf_in_unicast_promisc(9)ice_vf_get_promisc_masks(9)ice_vf_clear_all_promisc_modes(9)ice_vf_set_vsi_promisc(9)ice_vf_clear_vsi_promisc(9)ice_reset_vf_mbx_cnt(9)ice_reset_all_vfs(9)ice_notify_vf_reset(9)ice_reset_interrupts(9)ice_reset_vf(9)ice_set_vf_state_dis(9)ice_initialize_vf_entry(9)ice_dis_vf_qs(9)ice_err_to_virt_err(9)ice_check_vf_init(9)ice_vf_get_port_info(9)ice_cfg_mac_antispoof(9)ice_vsi_ena_spoofchk(9)ice_vsi_dis_spoofchk(9)ice_vsi_apply_spoofchk(9)ice_is_vf_trusted(9)ice_vf_has_no_qs_ena(9)ice_is_vf_link_up(9)ice_vf_ctrl_invalidate_vsi(9)ice_vf_ctrl_vsi_release(9)ice_vf_ctrl_vsi_setup(9)ice_vf_init_host_cfg(9)ice_vf_invalidate_vsi(9)ice_vf_vsi_release(9)ice_get_vf_ctrl_vsi(9)ice_vf_update_mac_lldp_num(9)
that's the whole crew, iykyk π§π
ngl if you got this far you're a real one. go touch some ice_vsi structs, bestie πβ
and that's a wrap! this page lived in ./drivers/net/ethernet/intel/ice, fresh from October 2026, and it's titled ice_vf_rebui...tor_node_cfg(9) β yeah, the truncated one, that's her π
π love that for us, bye bestie! πβ¨
π¦ 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