rust/zerocopy/benches/try_transmute_ref_dynamic_size.x86-64.mca
Source file repositories/reference/linux-study-clean/rust/zerocopy/benches/try_transmute_ref_dynamic_size.x86-64.mca
File Facts
- System
- Linux kernel
- Corpus path
rust/zerocopy/benches/try_transmute_ref_dynamic_size.x86-64.mca- Extension
.mca- Size
- 1403 bytes
- Lines
- 50
- 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
Iterations: 100
Instructions: 500
Total Cycles: 209
Total uOps: 700
Dispatch Width: 4
uOps Per Cycle: 3.35
IPC: 2.39
Block RThroughput: 1.8
Instruction Info:
[1]: #uOps
[2]: Latency
[3]: RThroughput
[4]: MayLoad
[5]: MayStore
[6]: HasSideEffects (U)
[1] [2] [3] [4] [5] [6] Instructions:
1 1 0.50 lea rdx, [rsi + 1]
1 0 0.25 xor eax, eax
2 6 0.50 * cmp word ptr [rdi], -16192
2 2 0.67 cmove rax, rdi
1 1 1.00 U ret
Resources:
[0] - SBDivider
[1] - SBFPDivider
[2] - SBPort0
[3] - SBPort1
[4] - SBPort4
[5] - SBPort5
[6.0] - SBPort23
[6.1] - SBPort23
Resource pressure per iteration:
[0] [1] [2] [3] [4] [5] [6.0] [6.1]
- - 1.50 1.51 - 1.99 0.50 0.50
Resource pressure by instruction:
[0] [1] [2] [3] [4] [5] [6.0] [6.1] Instructions:
- - 0.51 0.49 - - - - lea rdx, [rsi + 1]
- - - - - - - - xor eax, eax
- - - 0.02 - 0.98 0.50 0.50 cmp word ptr [rdi], -16192
- - 0.99 1.00 - 0.01 - - cmove rax, rdi
- - - - - 1.00 - - 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.