Performance/area efficiency in chip multiprocessors with micro-caches

Michela Becchi, Mark A. Franklin, Patrick J. Crowley

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

1 Scopus citations

Abstract

This paper proposes the use of very small instruction caches, called micro-caches (-caches), consisting of tens to hundreds of bytes, at the bottom of the instruction delivery hierarchy in chip-multiprocessors (CMP). Multi-core architectures place a novel emphasis on the performance/area efficiency of processor cores, and we note that traditional instruction cache sizes reflect an emphasis on hit-rate performance rather than efficiency. In brief, -caches reduce the area footprint of individual cores, thus allowing additional cores to fit within a given die area. We use commercial design tools and a commercial processor core to evaluate this tradeoff in the context of high-performance networking, where CMP architectures have had their greatest commercial impact to date. Our results suggest that the use of u-caches can yield a 25% improvement in efficiency relative to traditional hierarchies. In our evaluation, we consider a range of architectural options (cluster organization, non-blocking caches, cache parameters) and justify our conclusions while accounting for the errors inherent in die area estimates.

Original languageEnglish
Title of host publication2007 Computing Frontiers, Conference Proceedings
Pages247-258
Number of pages12
DOIs
StatePublished - 2007
Event4th Conference On Computing Frontiers 2007 - Ischia, Italy
Duration: May 7 2007May 9 2007

Publication series

Name2007 Computing Frontiers, Conference Proceedings

Conference

Conference4th Conference On Computing Frontiers 2007
Country/TerritoryItaly
CityIschia
Period05/7/0705/9/07

Keywords

  • Cache hierarchies
  • Chip multiprocessor
  • Networking workload

Fingerprint

Dive into the research topics of 'Performance/area efficiency in chip multiprocessors with micro-caches'. Together they form a unique fingerprint.

Cite this