bond_3ad_up...tor_settings(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… bond_3ad_update_ad_actor_settings(9) β€” Kernel API Manual ✨

okay so bestie, welcome to the Kernel API Manual, and today's main character is bond_3ad_update_ad_actor_settings(9). no cap, it's a little one, but it matters 🫢


🌸 NAME 🌸

bond_3ad_update_ad_actor_settings β€” literally the function that reflects a change of actor settings over to the ports πŸ’–


✨ SYNOPSIS ✨

void bond_3ad_update_ad_actor_settings (struct bonding *bond );

that's it. that's the whole signature. she's void, she's simple, she ate πŸ”₯


πŸŽ€ ARGUMENTS πŸŽ€

  • bond β€” the bonding struct we're gonna work on. your whole bond device, basically. the one getting the glow-up πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the vibe: if an ad_actor setting gets changed, we can't just leave the individual port settings sitting there being all outdated and embarrassing 😭. nope β€” we gotta update the individual port settings so that the bond device actually uses the new values when it gets upped. think of it as syncing the group chat so nobody's still quoting the old pinned message 🫢

the way that this is basically just making sure everyone's on the same page before the bond device goes live again. iconic behavior, honestly πŸ‘‘

not me reminding you that this is about when it gets upped β€” like, the update happens now, the new values get used when it's upped. keep that energy ⭐

🌈 SEE ALSO 🌈

okay this is the long part, grab a snack πŸ“. all of these live in the kernel file ./drivers/net/bonding/bond_3ad.c:

like I said. a whole friend group πŸ’€ but every single one of them is valid and you should go say hi 🧚


and that's the page bestie!! πŸ’œ this one's from the source directory ./drivers/net/bonding, dated October 2026, and it's filed under bond_3ad_up...tor_settings(9) in the manual. slay, go update those actor settings, and remember: sync your ports before you up the bond πŸŽ€βœ¨πŸ‘‘

πŸ“¦ where this page comes from