net/sched/em_text.c
Source file repositories/reference/linux-study-clean/net/sched/em_text.c
File Facts
- System
- Linux kernel
- Corpus path
net/sched/em_text.c- Extension
.c- Size
- 3682 bytes
- Lines
- 164
- 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/slab.hlinux/module.hlinux/types.hlinux/kernel.hlinux/string.hlinux/skbuff.hlinux/textsearch.hlinux/tc_ematch/tc_em_text.hnet/pkt_cls.h
Detected Declarations
struct text_matchfunction em_text_matchfunction em_text_changefunction em_text_destroyfunction em_text_dumpfunction init_em_textfunction exit_em_textmodule init init_em_text
Annotated Snippet
module_init(init_em_text);
module_exit(exit_em_text);
MODULE_ALIAS_TCF_EMATCH(TCF_EM_TEXT);Annotation
- Immediate include surface: `linux/slab.h`, `linux/module.h`, `linux/types.h`, `linux/kernel.h`, `linux/string.h`, `linux/skbuff.h`, `linux/textsearch.h`, `linux/tc_ematch/tc_em_text.h`.
- Detected declarations: `struct text_match`, `function em_text_match`, `function em_text_change`, `function em_text_destroy`, `function em_text_dump`, `function init_em_text`, `function exit_em_text`, `module init init_em_text`.
- 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.