net/ipv4/tcp_illinois.c

File Facts

System

Linux kernel

Corpus path

net/ipv4/tcp_illinois.c

Extension

.c

Size

8557 bytes

Lines

361

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

Detected Declarations

• struct illinois
• function rtt_reset
• function tcp_illinois_init
• function tcp_illinois_acked
• function max_delay
• function avg_delay
• function alpha
• function Reno
• function update_params
• function tcp_illinois_state
• function tcp_illinois_cong_avoid
• function tcp_illinois_ssthresh
• function tcp_illinois_info
• function tcp_illinois_register
• function tcp_illinois_unregister
• module init tcp_illinois_register

Annotated Snippet

module_init(tcp_illinois_register);
module_exit(tcp_illinois_unregister);

MODULE_AUTHOR("Stephen Hemminger, Shao Liu");
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("TCP Illinois");
MODULE_VERSION("1.0");

Annotation

• Immediate include surface: `linux/module.h`, `linux/skbuff.h`, `linux/inet_diag.h`, `asm/div64.h`, `net/tcp.h`.
• Detected declarations: `struct illinois`, `function rtt_reset`, `function tcp_illinois_init`, `function tcp_illinois_acked`, `function max_delay`, `function avg_delay`, `function alpha`, `function Reno`, `function update_params`, `function tcp_illinois_state`.
• 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.