lib/crypto/arm/chacha.h
Source file repositories/reference/linux-study-clean/lib/crypto/arm/chacha.h
File Facts
- System
- Linux kernel
- Corpus path
lib/crypto/arm/chacha.h- Extension
.h- Size
- 3127 bytes
- Lines
- 115
- Domain
- Kernel Services
- Bucket
- lib
- Inferred role
- Kernel Services: implementation source
- Status
- source 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
crypto/internal/simd.hlinux/jump_label.hlinux/kernel.hasm/cputype.hasm/hwcap.hasm/simd.h
Detected Declarations
function neon_usablefunction chacha_doneonfunction hchacha_block_archfunction chacha_crypt_archfunction chacha_mod_init_arch
Annotated Snippet
switch (read_cpuid_part()) {
case ARM_CPU_PART_CORTEX_A7:
case ARM_CPU_PART_CORTEX_A5:
/*
* The Cortex-A7 and Cortex-A5 do not perform well with
* the NEON implementation but do incredibly with the
* scalar one and use less power.
*/
break;
default:
static_branch_enable(&use_neon);
}
}
}
Annotation
- Immediate include surface: `crypto/internal/simd.h`, `linux/jump_label.h`, `linux/kernel.h`, `asm/cputype.h`, `asm/hwcap.h`, `asm/simd.h`.
- Detected declarations: `function neon_usable`, `function chacha_doneon`, `function hchacha_block_arch`, `function chacha_crypt_arch`, `function chacha_mod_init_arch`.
- Atlas domain: Kernel Services / lib.
- Implementation status: source 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.