ice_lag_move...gle_vf_nodes(9)

📦 version 7.3.1, in nixpkgs unstable

✨ ice_lag_move_single_vf_nodes — the Kernel API manual, bestie edition ✨

okay so real talk, this is a page from the Kernel API Manual (the (9) section, devs only, no cap) and today's main character is ice_lag_move_single_vf_nodes. Yes it's a long name. No we're not renaming it. 💅

🎀 NAME 🎀

ice_lag_move_single_vf_nodes — moves the Tx scheduling nodes for a single VF. that's it, that's the whole job. one VF, one move. slay.

🦋 SYNOPSIS 🦋

void ice_lag_move_single_vf_nodes (struct ice_lag *lag , u8 oldport , u8
newport , u16 vsi_num );

returns nothing (void, she's giving "I do the work and I don't need applause"), and it takes exactly four things. scroll down for the four things ⬇️

🌸 ARGUMENTS 🌸

  • lag — the primary interface LAG struct. this is the home base, the mothership, the struct ice_lag * everything hangs off of 🫶
  • oldport — the lport of the interface it's coming from. the "before" picture. a u8.
  • newport — the lport of the destination interface. the "after" picture. also a u8.
  • vsi_num — the SW index of the VF's VSI. the u16 that tells you which VF we're moving. it's giving coordinates, honestly 🎯

💜 SEE ALSO 💜

okay there are a LOT of siblings in this family and ngl they all showed up to the group chat, so here's the full roster, every single one, no gatekeeping:

and where does all this live? in the Kernel file 📁

./drivers/net/ethernet/intel/ice/ice_lag.c

that's the source file, right there, go read it, she's iconic.

✿ sign-off time ✿

so that's the page, bestie! 💖 it shipped from ./drivers/net/ethernet/intel/ice, dated October 2026, and it answers to the name ice_lag_move_single_vf_nodes(9) — same energy as the title up top, periodt. go move some VF nodes, you've got this 🌈✨🎀

📦 where this page comes from