ENTRY FRAME SIZE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… Entry frame size πŸ’…

okay bestie so we're in the Kernel API Manual today and this page is literally all about frame sizes for the rt2x00 wireless situation β€” it's short, it's sweet, and it's giving "one paragraph but make it iconic" ✨


πŸŽ€ Entry frame size πŸŽ€

Ralink PCI devices demand the Frame size be a multiple of 128 bytes β€” like, that's the rule, no notes, non-negotiable πŸ’…

For USB devices this restriction does not apply β€” but the value of 2432 still makes sense, because it's big enough to contain the maximum fragment size according to the ieee802.11 specs. so like, even though nobody's forcing you, 2432 just vibes πŸ¦‹

The aggregation size depends on support from the driver, but should be something around 3840 bytes. iykyk 🫢

ngl these numbers are the whole personality of this page β€” 128, 2432, 3840 β€” memorize them or at least screenshot it πŸ“Έ

πŸ”— SEE ALSO πŸ”—

the full squad, all of them, no skips, no cuts πŸ”₯ (and yeah, it starts with a whole header file, because of course it does):


and that's the whole page, bestie β€” short king energy πŸ‘‘ source situation is ./drivers/net/wireless/ralink/... (yes it's literally cut off with an ellipsis in the original, that's just how it is, don't come for me πŸ™ˆ) and it's dated October 2026. mwah, go read a queue macro, ily πŸ’œ

πŸ“¦ where this page comes from