net/ipv4/tcp_cdg.c

File Facts

System

Linux kernel

Corpus path

net/ipv4/tcp_cdg.c

Extension

.c

Size

11482 bytes

Lines

429

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.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/random.h
• linux/module.h
• linux/sched/clock.h
• net/tcp.h

Detected Declarations

• struct cdg_minmax
• struct cdg
• enum cdg_state
• function exp
• function cwnd
• function tcp_cdg_grad
• function tcp_cdg_backoff
• function tcp_cdg_cong_avoid
• function tcp_cdg_acked
• function tcp_cdg_ssthresh
• function tcp_cdg_cwnd_event
• function tcp_cdg_init
• function tcp_cdg_release
• function tcp_cdg_register
• function tcp_cdg_unregister
• module init tcp_cdg_register

Annotated Snippet

module_init(tcp_cdg_register);
module_exit(tcp_cdg_unregister);
MODULE_AUTHOR("Kenneth Klette Jonassen");
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("TCP CDG");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/random.h`, `linux/module.h`, `linux/sched/clock.h`, `net/tcp.h`.
• Detected declarations: `struct cdg_minmax`, `struct cdg`, `enum cdg_state`, `function exp`, `function cwnd`, `function tcp_cdg_grad`, `function tcp_cdg_backoff`, `function tcp_cdg_cong_avoid`, `function tcp_cdg_acked`, `function tcp_cdg_ssthresh`.
• 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.