net/netfilter/ipvs/ip_vs_nq.c

File Facts

System

Linux kernel

Corpus path

net/netfilter/ipvs/ip_vs_nq.c

Extension

.c

Size

3368 bytes

Lines

139

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/kernel.h
• net/ip_vs.h

Detected Declarations

• function delay
• function ip_vs_nq_schedule
• function list_for_each_entry_rcu
• function ip_vs_nq_init
• function ip_vs_nq_cleanup
• module init ip_vs_nq_init

Annotated Snippet

module_init(ip_vs_nq_init);
module_exit(ip_vs_nq_cleanup);
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("ipvs never queue scheduler");

Annotation

• Immediate include surface: `linux/module.h`, `linux/kernel.h`, `net/ip_vs.h`.
• Detected declarations: `function delay`, `function ip_vs_nq_schedule`, `function list_for_each_entry_rcu`, `function ip_vs_nq_init`, `function ip_vs_nq_cleanup`, `module init ip_vs_nq_init`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.