lib/crc/arm/crc64-neon.h
Source file repositories/reference/linux-study-clean/lib/crc/arm/crc64-neon.h
File Facts
- System
- Linux kernel
- Corpus path
lib/crc/arm/crc64-neon.h- Extension
.h- Size
- 775 bytes
- Lines
- 35
- 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.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
function pmull64function pmull64_highfunction pmull64_hi_lo
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-only
static inline uint64x2_t pmull64(uint64x2_t a, uint64x2_t b)
{
uint64_t l = vgetq_lane_u64(a, 0);
uint64_t m = vgetq_lane_u64(b, 0);
uint64x2_t result;
asm("vmull.p64 %q0, %P1, %P2" : "=w"(result) : "w"(l), "w"(m));
return result;
}
static inline uint64x2_t pmull64_high(uint64x2_t a, uint64x2_t b)
{
uint64_t l = vgetq_lane_u64(a, 1);
uint64_t m = vgetq_lane_u64(b, 1);
uint64x2_t result;
asm("vmull.p64 %q0, %P1, %P2" : "=w"(result) : "w"(l), "w"(m));
return result;
}
static inline uint64x2_t pmull64_hi_lo(uint64x2_t a, uint64x2_t b)
{
uint64_t l = vgetq_lane_u64(a, 1);
uint64_t m = vgetq_lane_u64(b, 0);
uint64x2_t result;
asm("vmull.p64 %q0, %P1, %P2" : "=w"(result) : "w"(l), "w"(m));
return result;
}
Annotation
- Detected declarations: `function pmull64`, `function pmull64_high`, `function pmull64_hi_lo`.
- 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.