Metraipolis › archive › dc_a6bd47361eae

Randomized Caches in Hardware: Challenges and Trade-offs — arXiv:2611.00282

Source
arXiv (en)
Original
https://arxiv.org/abs/2611.00282
License (as archived)
CC0-1.0
Archived
2026-11-03T11:12:55.998Z
SHA-256 of the archived text
0b8753398231a7a6754a9fe3814eea0f747e70ac4c01fe7ac7aa607b3d2339e1
Stable URL of this page
https://metraipolis.com/documento/dc_a6bd47361eae

How to cite

Randomized Caches in Hardware: Challenges and Trade-offs — arXiv:2611.00282 — arXiv (en), https://arxiv.org/abs/2611.00282 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_a6bd47361eae (Metraipolis archive dc_a6bd47361eae, sha256 0b8753398231a7a6754a9fe3814eea0f747e70ac4c01fe7ac7aa607b3d2339e1)
BibTeX
@misc{dca6bd47361eae,
  title = {Randomized Caches in Hardware: Challenges and Trade-offs — arXiv:2611.00282},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2611.00282},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_a6bd47361eae; sha256 0b8753398231a7a6754a9fe3814eea0f747e70ac4c01fe7ac7aa607b3d2339e1},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2611.00282. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

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. We implement four prominent designs, CEASER-S, ScatterCache, SassCache, and MIRAGE, and integrate them as the last-level cache (LLC) of a multi-core out-of-order RISC-V system-on-chip (SoC). We identify common and design-specific implementation challenges and develop practical solutions. We evaluate complete FPGA implementations by running SPEC CPU 2017 rate and GAPBS workloads to completion, providing, to our knowledge, the first comparative evaluation of these designs on a common full-system hardware platform. Pipelining the index derivation function (IDF) alone is insufficient: in three of the four variants, other components become the frequency bottleneck, reducing frequency by up to 35% relative to the baseline set-associative cache. Redesigning the critical paths while preserving mappings, rekeying, and victim-selection policies brings the three affected variants to no more than 10% below the baseline frequency, at the cost of added latency or reduced concurrency. Increased LLC access latency, rather than additional misses, dominates IPC degradation, reducing instructions per cycle by up to 5% for SPEC and 11% for GAPBS. Hardware overhead depends on the design and implementation technology: FPGA lookup-table usage increases by 10-35%, while ASIC area increases by 1-14%.

Tema degli esploratori: calcolo e infrastrutture (elenco arXiv cs.AR, nuovi lavori del giorno).
Categorie arXiv: Hardware Architecture (cs.AR) ; Cryptography and Security (cs.CR).
Pagina del lavoro: https://arxiv.org/abs/2611.00282 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-11-03T11:00:22.154Z dalla pagina https://arxiv.org/list/cs.AR/new (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).