ice_lag_monitor_act_bkup(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ice_lag_monitor_act_bkup(9) πŸ’…

okay bestie, welcome to the Kernel API Manual ✨ β€” this little cutie lives in ice_lag_monitor_act_bkup(9) and she's about to make your whole week. grab a matcha, we're going in πŸ“


🌸 NAME 🌸

ice_lag_monitor_act_bkup β€” literally just keeping track of which port is the active one in A/B LAG πŸ’– no cap, that's the whole job.


✨ SYNOPSIS ✨

void ice_lag_monitor_act_bkup (struct ice_lag *lag , struct
       netdev_bonding_info *b_info , struct net_device *event_netdev );

it's giving "void function, three args, zero drama" 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • lag β€” the lag info struct, bestie. this is the main character πŸ‘‘
  • b_info β€” bonding info. yes, the bonding. like the ports are in a situationship πŸ’€
  • event_netdev β€” the net_device that got the target netdev πŸ¦‹ (iykyk)

πŸ”₯ DESCRIPTION πŸ”₯

so the way this works: this function is for the primary PF to monitor changes in which port is active, and to handle those changes for SRIOV VF functionality. periodt. πŸ’…

that's it, that's the vibe check β€” primary PF watches, port switches up, SRIOV VF functionality gets handled. slay. ✨


πŸ’œ SEE ALSO πŸ’œ

okay this list is LONG but we are not skipping a single one, because every reference ate and left no crumbs 🌈 the kernel file herself:

  • Kernel file ./drivers/net/ethernet/intel/ice/ice_lag.c

and the whole friend group (39 of them, we counted, obsessed) πŸ‘‘:


ngl this one is genuinely a short read (some of these pages are 40 options long 😭) so enjoy the rare W, bestie πŸ’€

and that's the whole page! courtesy of ./drivers/net/ethernet/intel/ice, dated October 2026 β€” mwah, drink water, and may your primary PF always know which port is active πŸ’–βœ¨πŸŽ€πŸ¦‹πŸ’…

πŸ“¦ where this page comes from