ice_lag_reclaim_vf_nodes(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ice_lag_reclaim_vf_nodes β€” the kernel API manual, but make it make sense πŸ’–

okay so bestie, you're reading the ice_lag_reclaim_vf_nodes(9) page from the Kernel API Manual, and honestly? it's a little one, but it's a vital little one. it's giving "small but booked and busy" energy. πŸŽ€


✨ NAME ✨

ice_lag_reclaim_vf_nodes β€” when the interface is leaving bond primary, it reclaims nodes 🫢

like, that's the whole vibe. interface peaces out of being the bond primary, and the nodes get reclaimed. no cap.


🌸 SYNOPSIS 🌸

void ice_lag_reclaim_vf_nodes (struct ice_lag *lag , struct ice_hw
*src_hw );

she takes two things and returns nothing β€” void queen, no notes, we love a function that doesn't overpromise πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • lag β€” the primary interface's lag struct πŸ‘‘ this is the main character of the operation
  • src_hw β€” the HW struct for the current node location πŸ“ like, where the node is living rn

🧚 SEE ALSO 🧚

okay so this is the part where the manpage goes absolutely feral with the cross-references β€” she knows everyone, she's connected, she's the networking friend who can get you into any party 🌈

the kernel file for this one is:

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

and now, the full friend group (iykyk):

like… sixty-something functions. she's that girl with the full contacts list, fr fr πŸ’€


lowkey a reminder that every one of those is a real (9) reference and every name above is copied exactly β€” don't be out here typing ice_lag_* and hoping for the best, bestie πŸ™ˆ

and that's the whole page! short, sweet, and to the point πŸ“ she lives in ./drivers/net/ethernet/intel/ice, the page is dated October 2026, and it's part of the Kernel API Manual πŸ§šβ€β™€οΈ ok bye, go read the other sixty-four pages, slay πŸ’œ

πŸ“¦ where this page comes from