ice_lag_move_vf_nodes_cfg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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 πŸ’–


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