net/ipv4/tcp_nv.c

File Facts

System

Linux kernel

Corpus path

net/ipv4/tcp_nv.c

Extension

.c

Size

16117 bytes

Lines

502

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

Detected Declarations

• struct tcpnv
• function tcpnv_reset
• function tcpnv_init
• function nv_get_bounded_rtt
• function tcpnv_cong_avoid
• function tcpnv_recalc_ssthresh
• function tcpnv_state
• function tcpnv_acked
• function seconds
• function small
• function tcpnv_get_info
• function tcpnv_register
• function tcpnv_unregister
• module init tcpnv_register

Annotated Snippet

module_init(tcpnv_register);
module_exit(tcpnv_unregister);

MODULE_AUTHOR("Lawrence Brakmo");
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("TCP NV");
MODULE_VERSION("1.0");

Annotation

• Immediate include surface: `linux/module.h`, `linux/math64.h`, `net/tcp.h`, `linux/inet_diag.h`.
• Detected declarations: `struct tcpnv`, `function tcpnv_reset`, `function tcpnv_init`, `function nv_get_bounded_rtt`, `function tcpnv_cong_avoid`, `function tcpnv_recalc_ssthresh`, `function tcpnv_state`, `function tcpnv_acked`, `function seconds`, `function small`.
• 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.