llc_rcv(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… llc_rcv(9) β€” the 802.2 era πŸ’…

okay so real talk, this is a page from the Kernel API Manual, and it's about llc_rcv β€” the 802.2 entry point from net lower layers. yes bestie, we're in the kernel, we're in LLC, we're thriving πŸ¦‹


✨ SYNOPSIS ✨

int llc_rcv (struct sk_buff *skb , struct net_device *dev , struct
packet_type *pt , struct net_device *orig_dev );

like, four arguments, one int coming back at you. she's giving "small function, big responsibility" πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • skb β€” the received pdu, aka the actual packet babe, the whole reason we're here πŸ“
  • dev β€” the device that receive pdu. the one who caught it πŸ’…
  • pt β€” packet type. yes. that's the whole description. iconic minimalism tbh 🫢
  • orig_dev β€” the original receive net device, the before picture, the source of truth ✨

🌸 DESCRIPTION 🌸

so when the system receives a 802.2 frame, this function gets called. periodt. that's the moment she enters the chat πŸ’¬

what she does: she checks SAP and connection of the received pdu, then passes the frame on to llc_{station,sap,conn}_rcv for sending to the proper state machine. like she's the friend who reads the group chat, figures out which conversation it belongs in, and forwards it to the right gc 😭 🧚

aaaand if the frame is related to a busy connection β€” meaning a connection is sending data right now β€” she queues this frame in that connection's backlog. no cap, she holds it. she's patient. she's organized. she's lowkey the backbone of the operation πŸ’€πŸ‘‘

not me being obsessed with a receive handler but here we are 🌈

πŸ¦‹ SEE ALSO πŸ¦‹

go read them, iykyk, they're literally the friend group of this function πŸ’–


and that's the page bestie πŸŽ€ β€” brought to you by ./net/llc, dated October 2026, filed under llc_rcv(9). mwah, slay, read your manpages πŸ’œβ­πŸ”₯

πŸ“¦ where this page comes from