net/ipv4/tcp_veno.c

File Facts

System

Linux kernel

Corpus path

net/ipv4/tcp_veno.c

Extension

.c

Size

6082 bytes

Lines

245

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

Detected Declarations

• struct veno
• function data
• function veno_disable
• function tcp_veno_init
• function tcp_veno_pkts_acked
• function tcp_veno_state
• function tcp_veno_cwnd_event
• function tcp_veno_cwnd_event_tx_start
• function tcp_veno_cong_avoid
• function tcp_veno_ssthresh
• function tcp_veno_register
• function tcp_veno_unregister
• module init tcp_veno_register

Annotated Snippet

module_init(tcp_veno_register);
module_exit(tcp_veno_unregister);

MODULE_AUTHOR("Bin Zhou, Cheng Peng Fu");
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("TCP Veno");

Annotation

• Immediate include surface: `linux/mm.h`, `linux/module.h`, `linux/skbuff.h`, `linux/inet_diag.h`, `net/tcp.h`.
• Detected declarations: `struct veno`, `function data`, `function veno_disable`, `function tcp_veno_init`, `function tcp_veno_pkts_acked`, `function tcp_veno_state`, `function tcp_veno_cwnd_event`, `function tcp_veno_cwnd_event_tx_start`, `function tcp_veno_cong_avoid`, `function tcp_veno_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.