net/sched/sch_plug.c

File Facts

System

Linux kernel

Corpus path

net/sched/sch_plug.c

Extension

.c

Size

6624 bytes

Lines

231

Domain

Networking Core

Bucket

Sockets, Protocols, Packet Path, And Network Policy

Inferred role

Networking Core: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/types.h
• linux/kernel.h
• linux/errno.h
• linux/netdevice.h
• linux/skbuff.h
• net/pkt_sched.h

Detected Declarations

• struct plug_sched_data
• function plug_enqueue
• function plug_init
• function received
• function plug_module_init
• function plug_module_exit
• module init plug_module_init

Annotated Snippet

module_init(plug_module_init)
module_exit(plug_module_exit)
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("Qdisc to plug and unplug traffic via netlink control");

Annotation

• Immediate include surface: `linux/module.h`, `linux/types.h`, `linux/kernel.h`, `linux/errno.h`, `linux/netdevice.h`, `linux/skbuff.h`, `net/pkt_sched.h`.
• Detected declarations: `struct plug_sched_data`, `function plug_enqueue`, `function plug_init`, `function received`, `function plug_module_init`, `function plug_module_exit`, `module init plug_module_init`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• Implementation status: integration 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.