net/ipv4/tcp_lp.c

File Facts

System

Linux kernel

Corpus path

net/ipv4/tcp_lp.c

Extension

.c

Size

9560 bytes

Lines

358

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
• net/tcp.h

Detected Declarations

• struct lp
• enum tcp_lp_state
• function tcp_lp_init
• function tcp_lp_cong_avoid
• function tcp_lp_remote_hz_estimator
• function delay
• function tcp_lp_rtt_sample
• function tcp_lp_pkts_acked
• function tcp_lp_register
• function tcp_lp_unregister
• module init tcp_lp_register

Annotated Snippet

module_init(tcp_lp_register);
module_exit(tcp_lp_unregister);

MODULE_AUTHOR("Wong Hoi Sing Edison, Hung Hing Lun Mike");
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("TCP Low Priority");

Annotation

• Immediate include surface: `linux/module.h`, `net/tcp.h`.
• Detected declarations: `struct lp`, `enum tcp_lp_state`, `function tcp_lp_init`, `function tcp_lp_cong_avoid`, `function tcp_lp_remote_hz_estimator`, `function delay`, `function tcp_lp_rtt_sample`, `function tcp_lp_pkts_acked`, `function tcp_lp_register`, `function tcp_lp_unregister`.
• 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.