lib/raid/xor/xor-core.c
Source file repositories/reference/linux-study-clean/lib/raid/xor/xor-core.c
File Facts
- System
- Linux kernel
- Corpus path
lib/raid/xor/xor-core.c- Extension
.c- Size
- 5122 bytes
- Lines
- 195
- Domain
- Kernel Services
- Bucket
- lib
- Inferred role
- Kernel Services: exported/initcall integration point
- Status
- integration implementation candidate
Why This File Exists
Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.
- Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.
- 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/module.hlinux/gfp.hlinux/slab.hlinux/raid/xor.hlinux/jiffies.hlinux/preempt.hlinux/static_call.hxor_impl.hxor_arch.h
Detected Declarations
function xor_genfunction xor_forcefunction xor_registerfunction do_xor_speedfunction calibrate_xor_blocksfunction arch_xor_initfunction xor_initfunction xor_exitmodule init xor_initexport xor_gen
Annotated Snippet
core_initcall(xor_init);
module_exit(xor_exit);Annotation
- Immediate include surface: `linux/module.h`, `linux/gfp.h`, `linux/slab.h`, `linux/raid/xor.h`, `linux/jiffies.h`, `linux/preempt.h`, `linux/static_call.h`, `xor_impl.h`.
- Detected declarations: `function xor_gen`, `function xor_force`, `function xor_register`, `function do_xor_speed`, `function calibrate_xor_blocks`, `function arch_xor_init`, `function xor_init`, `function xor_exit`, `module init xor_init`, `export xor_gen`.
- Atlas domain: Kernel Services / lib.
- 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.