__record_pdu(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __record_pdu(9) β€” the linux kernel API manual, but make it make sense

okay so this one lives in the 9 section of the kernel API manual and honestly? it's a little baby function doing grown-up LACP stuff. let's get into it 🫢


🌸 NAME 🌸

__record_pdu β€” record parameters from a received lacpdu. that's it. that's the whole vibe. it takes the tea from an incoming lacpdu and writes it down πŸ“


✨ SYNOPSIS ✨

void __record_pdu (struct lacpdu *lacpdu , struct port *port );

note the void bestie β€” this one doesn't hand anything back. it just does the thing and dips πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • lacpdu β€” the lacpdu we've received. like, the actual packet that just showed up. this is the mail, we're about to open it πŸ“¬
  • port β€” the port we're looking at. this is the main character of the whole operation, no cap πŸ‘‘

πŸ’– DESCRIPTION πŸ’–

so what does it do? it takes the parameter values for the Actor that were carried in a received lacpdu, and records them as the current partner operational parameter values. basically: whoever we just heard from is now officially our partner, and their deets go in the book πŸ“–βœ¨

and then, the finishing move β€” it sets actor_oper_port_state.defaulted to FALSE. yes queen, we are no longer defaulted. we are known. periodt πŸŽ‰


πŸ¦‹ SEE ALSO πŸ¦‹

okay, this list is LONG, grab a snack πŸ“ β€” and heads up, these all live in the kernel file ./drivers/net/bonding/bond_3ad.c, so keep that in mind:

like, literally the entire 3ad friend group 😭 go say hi to all of them


ngl if you're reading this because you're deep in bonding driver internals at 2am β€” hydrate, bestie πŸ’§ you're doing amazing πŸ’œ

and that's the page! 🌈 sourced from ./drivers/net/bonding, dated October 2026 β€” catch you in the next manpage, mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from