ice_lag_move_vf_node_tc(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ice_lag_move_vf_node_tc(9) — the Kernel API Manual ✨

okay so bestie, we're in the kernel docs, specifically the ice LAG party 🧊, and this page is ice_lag_move_vf_node_tc(9). Yes that's a mouthful. Yes it slays. Let's get into it 🎀

🌸 NAME 🌸

ice_lag_move_vf_node_tc — move scheduling nodes for one VF on one TC 💫

✨ SYNOPSIS ✨

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

it returns void btw — no return value, no drama, it just does the thing 🫶

🦋 ARGUMENTS 🦋

  • lag — the lag info struct 💖 like, the whole vibe container
  • oldport — lport of previous nodes location 👋 where the nodes were chillin' before
  • newport — lport of destination nodes location 🚚 where they're headed
  • vsi_num — array index of VSI in PF space 🔢 (yes it's an index, not a count, noted 👑)
  • tc — traffic class to move 🌈 the specific TC getting relocated

💀 SEE ALSO 💀

no cap, this cross-reference list is long — grab a snack, bestie 🍓

like I said. iconic list. ate. 👑

quick vibe check 💅 — nothing here says what happens if you pass a bad port or a TC that doesn't exist, so don't come for me, I'm literally just reading the page 📖

and that's the whole thing, bestie 🫶 this page is from ./drivers/net/ethernet/intel/ice and it's dated October 2026, filed under ice_lag_move_vf_node_tc(9) — go forth and move those scheduling nodes, you've got this 🦋💖✨

📦 where this page comes from