IPTFS_DEFAUL...X_QUEUE_SIZE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ IPTFS_DEFAULT_MAX_QUEUE_SIZE ✨

okay bestie, welcome to the Kernel API Manual πŸ’… this one's a teeny tiny little page but she's iconic in her own way β€” it's all about IPTFS_DEFAULT_MAX_QUEUE_SIZE, so let's get into it 🫢


🌸 NAME 🌸

IPTFS_DEFAULT_MAX_QUEUE_SIZE β€” the default max output queue size, periodt πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

IPTFS_DEFAULT_MAX_QUEUE_SIZE

literally just the thing itself, no arguments, no drama ✨


πŸŽ€ DESCRIPTION πŸŽ€

so this is the default IPTFS max output queue size, measured in octets πŸ“ and like… what even is the output queue? okay so picture this: packets come in, they're destined to go out over an IPTFS tunnel, and they get stored in the output queue first β€” hanging out there before they're output over the IPTFS tunnel in aggregated/fragmented form. that's the whole vibe πŸ’«

Default is 1M. yes bestie, one meg. she's generous πŸ‘‘


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./net/xfrm/xfrm_iptfs.c β€” go read the source, iykyk πŸ“–πŸ’œ and also all of these lovelies:

like, that's the whole friend group right there πŸ˜­πŸ’•


and that's the page!! mwah πŸ’‹ sign-off time: this lil beauty comes from ./net/xfrm, dated October 2026, and yes she's still IPTFS_DEFAUL...X_QUEUE_SIZE(9) at the bottom too because symmetry is everything πŸŽ€βœ¨ go forth and queue responsibly, bestie πŸŒˆπŸ‘‘

πŸ“¦ where this page comes from