ice_lag_move_vf_nodes_sync(9)
π
ice_lag_move_vf_nodes_sync(9) β the kernel API manual page, but make it make sense
okay so this is ice_lag_move_vf_nodes_sync from section 9 of the Kernel API Manual, and bestie, it's giving "tiny function, huge job." let's get into it π«Ά
β¨ NAME β¨
ice_lag_move_vf_nodes_sync β move vf nodes to active interface
like literally that's the whole vibe: VF nodes? moved. active interface? that's where they're going. no cap π
π¦ SYNOPSIS π¦
void ice_lag_move_vf_nodes_sync (struct ice_lag *lag , struct ice_hw
*dest_hw );
returns void, so likeβ¦ it doesn't hand you anything back. it just does the thing. main character energy fr fr π
πΈ ARGUMENTS πΈ
lagβ the primary interface's lag struct. this is the β¨primaryβ¨ one, okay, keep that straight.dest_hwβ the lport value for the currently active port. yes, an lport value. yes, it's important. π
π DESCRIPTION π
okay so here's the tea β β this function is used in a reset context, i.e. outside of event handling. not in the event handler, bestie, we are past that.
what it does: it moves the VF nodes over to the secondary interface when that interface is the active interface during a reset rebuild. so during the rebuild chaos, whoever's actually active gets the VF nodes. slay. π β¨
that's it. that's the whole function. short and iconic, we love a concise queen π
π§ SEE ALSO π§
first up, the source file (iykyk):
Kernel file ./drivers/net/ethernet/intel/ice/ice_lag.c
and now the whole entire friend group β every single one of these, no skipping, I see you π:
ice_lag_set_primary(9)ice_lag_set_bkup(9)netif_is_same_ice(9)ice_lag_config_eswitch(9)ice_netdev_to_lag(9)ice_lag_find_hw_by_lport(9)ice_pkg_has_lport_extract(9)ice_lag_find_primary(9)ice_lag_cfg_fltr(9)ice_lag_cfg_dflt_fltr(9)ice_lag_cfg_drop_fltr(9)ice_lag_cfg_pf_fltrs_act_bkup(9)ice_lag_cfg_lp_fltr(9)ice_lag_cfg_pf_fltrs(9)ice_display_lag_info(9)ice_lag_qbuf_recfg(9)ice_lag_get_sched_parent(9)ice_lag_move_vf_node_tc(9)ice_lag_build_netdev_list(9)ice_lag_destroy_netdev_list(9)ice_lag_move_single_vf_nodes(9)ice_lag_move_vf_nodes(9)ice_lag_move_vf_nodes_cfg(9)ice_lag_prepare_vf_reset(9)ice_lag_complete_vf_reset(9)ice_lag_info_event(9)ice_lag_aa_qbuf_recfg(9)ice_lag_aa_move_vf_qs(9)ice_lag_aa_failover(9)ice_lag_reclaim_vf_tc(9)ice_lag_reclaim_vf_nodes(9)ice_lag_link(9)ice_lag_act_bkup_unlink(9)ice_lag_aa_unlink(9)ice_lag_link_unlink(9)ice_lag_set_swid(9)ice_lag_primary_swid(9)ice_lag_add_prune_list(9)ice_lag_del_prune_list(9)ice_lag_init_feature_support_flag(9)ice_lag_changeupper_event(9)ice_lag_monitor_link(9)ice_lag_monitor_act_bkup(9)ice_lag_aa_clear_spoof(9)ice_lag_monitor_act_act(9)ice_lag_monitor_info(9)ice_lag_chk_comp(9)ice_lag_unregister(9)ice_lag_monitor_rdma(9)ice_lag_chk_disabled_bond(9)ice_lag_disable_sriov_bond(9)ice_lag_preset_drop_fltr(9)ice_lag_process_event(9)ice_lag_event_handler(9)ice_register_lag_handler(9)ice_unregister_lag_handler(9)ice_create_lag_recipe(9)ice_lag_move_vf_nodes_tc_sync(9)ice_init_lag(9)ice_deinit_lag(9)ice_lag_rebuild(9)ice_lag_is_switchdev_running(9)
that's sixty-something functions and every single one made the list. obsessed with the commitment honestly π
heads up bestie: this one lives under ./drivers/net/ethernet/intel/ice in the kernel tree β that's the ice driver, the intel ethernet one. go touch grass in the source if you need more deets π
kk that's the page!! written in October 2026, from the ./drivers/net/ethernet/intel/ice corner of the kernel, and it's the ice_lag_move_vf_nodes_sync(9) manual page β bye bestie, go move some VF nodes πβ¨π¦
π¦ 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