__update_ntt(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __update_ntt(9) β€” Kernel API Manual, bestie edition πŸŽ€

okay so first of all, this is a page from the Kernel API Manual (section 9, the kernel-functions girlies) and it's literally all about __update_ntt. yes we're in the bonding driver. yes it's about LACP. no you don't have to be scared. sit down, bestie, I got you 🫢


✨ NAME ✨

__update_ntt β€” update a port's ntt variable from a received lacpdu

like, that's the whole gig. one tiny flag, one big vibe check. πŸ’…


🌸 SYNOPSIS 🌸

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

returns nothing, changes something. classic. no cap.


πŸ¦‹ ARGUMENTS πŸ¦‹

  • lacpdu β€” the lacpdu we've received. this is the incoming tea β˜•, freshly delivered.
  • port β€” the port we're looking at. the main character whose ntt we're about to maybe touch πŸ”₯

πŸ’– DESCRIPTION πŸ’–

So. The whole job here is updating the value of the ntt variable, using parameter values from a newly received lacpdu. That's it. That's the function. πŸŽ€

Here's the lore: the parameter values for the partner carried in the received PDU get compared with the corresponding operational parameter values for the Actor. Think of it like a vibe check between what your partner says they are and what your actual live settings are. πŸ‘‘

If one or more of the comparisons shows that the value(s) received in the PDU differ from the current operational values, then ntt is set to TRUE. Basically: something changed, so ntt gets to be true, slay. ✨

Otherwise β€” and this is important, bestie β€” ntt remains unchanged. Not set to false. Not reset. Just left alone to live its life. 🧚

literally nothing happens in the "no diff" case, and that's on purpose. don't go reading extra behaviour into it πŸ™ˆ

🌈 SEE ALSO 🌈

the whole friend group, fr fr β€” all of these live in the kernel file ./drivers/net/bonding/bond_3ad.c:

that's fifty-seven besties. I counted. we're not doing "etc." in this house πŸ’€


okay that's the page!! this one's brought to you by ./drivers/net/bonding, dated October 2026, and it's serving Kernel API Manual energy from the very first line. go update your ntt, icon. πŸŒΈβœ¨πŸ‘‘

πŸ“¦ where this page comes from