SSH_PACKET_PRIORITY(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

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

okay so bestie, we're in the Kernel API Manual today and this little macro is genuinely iconic β€” it's the whole "who goes first" of the Surface Aggregator packet world πŸŽ€


✨ NAME ✨

SSH_PACKET_PRIORITY β€” literally computes the packet priority for you, out of the base priority plus how many tries it's had 🌸


πŸ¦‹ SYNOPSIS πŸ¦‹

SSH_PACKET_PRIORITY (base , try );

no cap, that's the whole vibe πŸ’œ


πŸŽ€ ARGUMENTS πŸŽ€

  • base β€” the base priority, given as the suffix of enum ssh_packet_base_priority, like FLUSH, DATA, ACK, or NAK. iykyk πŸ”₯
  • try β€” the number of tries. and bestie, listen: it must be less than 16 😭 that's not a suggestion, that's the rule.

🌈 DESCRIPTION 🌈

so it computes the combined packet priority, right? and the way it works is that the combined priority is dominated by the base priority πŸ‘‘ β€” like, base priority is the main character here.

meanwhile the number of (re-)tries decides the precedence of packets that have the same base priority. and the packets that already have more tries? they get higher priority. periodt πŸ’…


⭐ RETURN ⭐

returns the computed priority as a value that fits inside a u8 🫢 and remember: a higher number means a higher priority. higher number = more important, no cap πŸ’–


πŸ” SEE ALSO πŸ”

okay this list is a journey, buckle up 🧚


and that's the page, bestie πŸŽ€ sign-off time: this one comes from ./include/linux/surface_aggreg... and it's dated October 2026 β€” SSH_PACKET_PRIORITY(9), ate and left no crumbs πŸ’€βœ¨

πŸ“¦ where this page comes from