A TRRIP Down Memory Lane: Temperature-Based Re-Reference Interval Prediction For Instruction Caching
This addresses performance bottlenecks in mobile systems with strict hardware and software constraints, offering a practical solution for improving CPU efficiency in resource-limited environments.
The paper tackles the problem of high instruction cache miss rates in modern mobile CPUs due to complex runtime behavior, by proposing TRRIP, a software-hardware co-design that uses code temperature analysis to optimize cache replacement, resulting in a 26.5% reduction in L2 MPKI for instructions and a 3.9% geomean speedup.
Modern mobile CPU software pose challenges for conventional instruction cache replacement policies due to their complex runtime behavior causing high reuse distance between executions of the same instruction. Mobile code commonly suffers from large amounts of stalls in the CPU frontend and thus starvation of the rest of the CPU resources. Complexity of these applications and their code footprint are projected to grow at a rate faster than available on-chip memory due to power and area constraints, making conventional hardware-centric methods for managing instruction caches to be inadequate. We present a novel software-hardware co-design approach called TRRIP (Temperature-based Re-Reference Interval Prediction) that enables the compiler to analyze, classify, and transform code based on "temperature" (hot/cold), and to provide the hardware with a summary of code temperature information through a well-defined OS interface based on using code page attributes. TRRIP's lightweight hardware extension employs code temperature attributes to optimize the instruction cache replacement policy resulting in the eviction rate reduction of hot code. TRRIP is designed to be practical and adoptable in real mobile systems that have strict feature requirements on both the software and hardware components. TRRIP can reduce the L2 MPKI for instructions by 26.5% resulting in geomean speedup of 3.9%, on top of RRIP cache replacement running mobile code already optimized using PGO.