Skip to content
NewA calmer, faster ZeroHour

arXiv evaluates randomized caches for side-channel protection

Original title: Randomized Caches in Hardware: Challenges and Trade-offs

arXiv cs.CRby Xinrui Wang ()1 min read
AI summary · x-ai/grok-4.7Summaries by Vani AI

FPGA implementation of four randomized cache designs in a multi-core RISC-V SoC shows pipelining alone insufficient and redesign needed to limit frequency loss to 10% below baseline.

Researchers implemented CEASER-S ScatterCache SassCache and MIRAGE as the last-level cache in a multi-core out-of-order RISC-V system-on-chip. They identified common and design-specific hardware challenges and developed practical solutions. Complete FPGA evaluations on SPEC CPU 2017 and GAPBS workloads revealed that increased LLC access latency dominates IPC degradation. Hardware overhead varies by design with FPGA LUT usage rising 10-35% and ASIC area 1-14%.

Key facts
  • Four prominent randomized cache designs implemented
  • Pipelining IDF alone insufficient in three variants
  • Redesigning critical paths limits frequency loss to 10%
  • Increased access latency reduces IPC by up to 5% for SPEC and 11% for GAPBS
  • First full-system comparative evaluation on common platform
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

1 min read at arxiv.org

Randomized caches protect against side-channel attacks by obfuscating the mapping of memory addresses to cache locations. Existing proposals typically describe architectural behavior, leaving practical hardware implementation challenges largely unexplored.

arXiv cs.CR

By Xinrui Wang · arxiv.org

Read the full article at arXiv cs.CR

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.