tipc_sk_overlimit2(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… tipc_sk_overlimit2 β€” the kernel API manual, bestie edition ✨

okay so picture this: we're deep in the Kernel API Manual (yeah, the tipc_sk_overlimit2(9) one, the sequel nobody saw coming 🎬) and this little function is out here doing a vibe check on your socket's rx queue. iconic behavior, honestly.


✨ NAME ✨

tipc_sk_overlimit2 β€” checks if the socket rx queue is like, about to be overloaded 🫣 and like… only the rcv queue gets considered, no cap. main character energy: one queue, one job.


πŸŽ€ SYNOPSIS πŸŽ€

bool tipc_sk_overlimit2 (struct sock *sk , struct sk_buff *skb );

like, it takes two things and gives you back a bool. simple. clean. slay πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • sk β€” the tipc sk that's getting checked, bestie. this is the socket we're side-eyeing πŸ‘€
  • skb β€” the tipc msg getting checked too, fr fr. it's coming along for the ride πŸš—

πŸ”₯ RETURN πŸ”₯

returns true if the socket's rx queue allocation is > 90% β€” like, almost full, we're sweating 😭 β€” otherwise it's false. that's it, that's the whole answer πŸ’€

ngl, keep an eye on that > 90% threshold, it's literally the entire point of this function 🌸

πŸ‘‘ SEE ALSO πŸ‘‘

bestie. buckle up. this list is LONG and we're reading every single one, no skipping πŸ™ˆ all of these live in the kernel file ./net/tipc/socket.c:


mwah πŸ’œ before you go β€” this whole thing ships from ./net/tipc, and the version/date stamp on it is October 2026. go forth and check those rx queues, queen πŸ‘‘βœ¨

πŸ“¦ where this page comes from