RISC-V Design · All levels
Extensions: Vector & Crypto: Tricky Q&A
Senior interview and review questions for Extensions: Vector & Crypto.
Section Q&A bank
Use these drills after completing all topics in Extensions: Vector & Crypto. Answer with workload framing, mechanism proof, owner, and release decision.
Why does RVV use vtype and vl instead of fixed architectural vector width?
diagram
[INT][RISCV][EXTENSIONS-VECTORS-CRYPTO]
Q: Why does RVV use vtype and vl instead of fixed architectural vector width?
A:
The variable-length model lets one binary scale from narrow to wide implementations while preserving semantics through tail and mask handling. Software expresses element type and requested length, and hardware chooses how much work each iteration completes based on VLEN. This protects portability and allows future cores to increase width without invalidating compiler and library assumptions.
FOLLOW-UP TRAP: Assuming RVV behaves like fixed-width SIMD and needs per-core binaries.What usually limits vector lane scaling before theoretical throughput is reached?
diagram
[INT][RISCV][EXTENSIONS-VECTORS-CRYPTO]
Q: What usually limits vector lane scaling before theoretical throughput is reached?
A:
The bottlenecks are often register-file bandwidth, load/store alignment behavior, cross-lane shuffle cost, and critical-path pressure in forwarding and hazard logic. Without balanced memory and scoreboard design, extra lanes raise peak capability but not sustained cycles-per-element. Practical scaling requires concurrent PPA closure, not just wider datapaths.
FOLLOW-UP TRAP: Projecting linear speedup from lane count alone.When should a design add dedicated crypto hardware instead of relying only on bitmanip instructions?
diagram
[INT][RISCV][EXTENSIONS-VECTORS-CRYPTO]
Q: When should a design add dedicated crypto hardware instead of relying only on bitmanip instructions?
A:
Dedicated paths are justified when target workloads need high sustained crypto throughput, strict latency bounds, or lower energy-per-operation than shared integer resources can provide. The decision also depends on side-channel hardening requirements and verification cost for constant-time guarantees. Bitmanip-only approaches are simpler but can miss product-level performance and security targets.
FOLLOW-UP TRAP: Choosing based only on instruction-count reduction without throughput and leakage analysis.How does an extension compatibility policy reduce long-term software fragmentation?
diagram
[INT][RISCV][EXTENSIONS-VECTORS-CRYPTO]
Q: How does an extension compatibility policy reduce long-term software fragmentation?
A:
It defines stable extension baselines per SKU class, enforces them through CI conformance tests, and aligns toolchain defaults with runtime feature discovery. That prevents accidental use of unsupported instructions and keeps dispatch logic predictable across deployments. Clear deprecation and migration rules let partners plan updates without breaking older systems.
FOLLOW-UP TRAP: Publishing extension lists without ABI, toolchain, and conformance enforcement.