net/ieee802154/6lowpan/6lowpan_i.h

File Facts

System

Linux kernel

Corpus path

net/ieee802154/6lowpan/6lowpan_i.h

Extension

.h

Size

1342 bytes

Lines

49

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

• linux/list.h
• net/ieee802154_netdev.h
• net/inet_frag.h
• net/6lowpan.h

Detected Declarations

• struct frag_lowpan_compare_key
• struct lowpan_frag_queue

Annotated Snippet

struct frag_lowpan_compare_key {
	u16 tag;
	u16 d_size;
	struct ieee802154_addr src;
	struct ieee802154_addr dst;
};

/* Equivalent of ipv4 struct ipq
 */
struct lowpan_frag_queue {
	struct inet_frag_queue	q;
};

int lowpan_frag_rcv(struct sk_buff *skb, const u8 frag_type);
void lowpan_net_frag_exit(void);
int lowpan_net_frag_init(void);

void lowpan_rx_init(void);
void lowpan_rx_exit(void);

int lowpan_header_create(struct sk_buff *skb, struct net_device *dev,
			 unsigned short type, const void *_daddr,
			 const void *_saddr, unsigned int len);
netdev_tx_t lowpan_xmit(struct sk_buff *skb, struct net_device *dev);

int lowpan_iphc_decompress(struct sk_buff *skb);
lowpan_rx_result lowpan_rx_h_ipv6(struct sk_buff *skb);

#endif /* __IEEE802154_6LOWPAN_I_H__ */

Annotation

• Immediate include surface: `linux/list.h`, `net/ieee802154_netdev.h`, `net/inet_frag.h`, `net/6lowpan.h`.
• Detected declarations: `struct frag_lowpan_compare_key`, `struct lowpan_frag_queue`.
• 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.