ice_lag_move_vf_nodes_cfg(9)
π ice_lag_move_vf_nodes_cfg β a whole kernel API manual moment β¨
okay so bestie, you're looking at ice_lag_move_vf_nodes_cfg(9) β that's the <cyan>Kernel API Manual</cyan> one, mwah π
πΈ NAME πΈ
ice_lag_move_vf_nodes_cfg β the function that moves vf nodes outside of LAG netdev event context. it's giving "we're doing this off the clock, respectfully" π
π¦ SYNOPSIS π¦
void ice_lag_move_vf_nodes_cfg (struct ice_lag *lag , u8 src_prt , u8
dst_prt );
like, three args, no return value, it just does the thing π₯
π ARGUMENTS π
lagβ the local lag struct. your main character, lowkey πsrc_prtβ the lport value for the source port, i.e. where we're moving from π«Άdst_prtβ the lport value for the destination port, i.e. where we're moving to β¨
π DESCRIPTION π
so this function is literally for moving nodes during an out-of-netdev-event situation β primarily when the driver needs to reconfigure or recreate resources. it's the "we're not in the event context rn, handle it anyway" vibe, fr fr π§
β οΈ okay this part is important: it must be called while holding the lag_mutex β no cap β to avoid lag events from processing while out-of-sync moves are happening. skipping that is not the move, bestie π
also, paired moves (like the ones used in a reset flow) should both be called under the same mutex lock, so nothing changes in between the start of the reset and the end of the reset. both under one lock, periodt π₯
π SEE ALSO π
- Kernel file:
./drivers/net/ethernet/intel/ice/ice_lag.cπ
and the whole squad, because the family is large and we love every single one of them π
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_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_lag_move_vf_nodes_sync(9),ice_init_lag(9),ice_deinit_lag(9),ice_lag_rebuild(9),ice_lag_is_switchdev_running(9)
so yeah, that's the whole page π go forth and hold that mutex, queen π
πΈπ
sigNed off with love from ./drivers/net/ethernet/intel/ice, dated October 2026 π
πΈ
π¦ 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