rust/zerocopy/benches/ref_from_bytes_with_elems_dynamic_padding.x86-64
Source file repositories/reference/linux-study-clean/rust/zerocopy/benches/ref_from_bytes_with_elems_dynamic_padding.x86-64
File Facts
- System
- Linux kernel
- Corpus path
rust/zerocopy/benches/ref_from_bytes_with_elems_dynamic_padding.x86-64- Extension
.x86-64- Size
- 291 bytes
- Lines
- 20
- Domain
- Rust Kernel Layer
- Bucket
- Rust API Membrane
- Inferred role
- Rust Kernel Layer: Rust API Membrane
- Status
- atlas-only
Why This File Exists
Rust-side wrappers and abstractions around kernel C APIs, ownership contracts, allocation, synchronization, and module integration.
- Rust-side wrappers and abstractions around kernel C APIs, ownership contracts, allocation, synchronization, and module integration.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
bench_ref_from_bytes_with_elems_dynamic_padding:
movabs rax, 3074457345618258598
cmp rdx, rax
seta cl
mov rax, rdi
test al, 3
setne dil
or dil, cl
jne .LBB5_2
lea rcx, [rdx + 2*rdx]
or rcx, 3
add rcx, 9
cmp rsi, rcx
je .LBB5_3
.LBB5_2:
xor eax, eax
mov rdx, rsi
.LBB5_3:
ret
Annotation
- Atlas domain: Rust Kernel Layer / Rust API Membrane.
- Implementation status: atlas-only.
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.