include/net/llc_sap.h

File Facts

System

Linux kernel

Corpus path

include/net/llc_sap.h

Extension

.h

Size

806 bytes

Lines

27

Domain

Networking Core

Bucket

Sockets, Protocols, Packet Path, And Network Policy

Inferred role

Networking Core: implementation source

Status

source implementation candidate

Why This File Exists

Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.

• Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• asm/types.h

Detected Declarations

• struct llc_sap
• struct net_device
• struct sk_buff
• struct sock

Annotated Snippet

#ifndef LLC_SAP_H
#define LLC_SAP_H

#include <asm/types.h>

/*
 * Copyright (c) 1997 by Procom Technology,Inc.
 * 		 2001-2003 by Arnaldo Carvalho de Melo <acme@conectiva.com.br>
 */
struct llc_sap;
struct net_device;
struct sk_buff;
struct sock;

void llc_sap_rtn_pdu(struct llc_sap *sap, struct sk_buff *skb);
void llc_save_primitive(struct sock *sk, struct sk_buff *skb,
			unsigned char prim);
struct sk_buff *llc_alloc_frame(struct sock *sk, struct net_device *dev,
				u8 type, u32 data_size);

void llc_build_and_send_test_pkt(struct llc_sap *sap, struct sk_buff *skb,
				 unsigned char *dmac, unsigned char dsap);
void llc_build_and_send_xid_pkt(struct llc_sap *sap, struct sk_buff *skb,
				unsigned char *dmac, unsigned char dsap);
#endif /* LLC_SAP_H */

Annotation

• Immediate include surface: `asm/types.h`.
• Detected declarations: `struct llc_sap`, `struct net_device`, `struct sk_buff`, `struct sock`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.