1. Samira Khan University of Virginia April 14, 2016 COMPUTER ARCHITECTURE CS 6354 Caches The content and concept of this course are adapted from CMU ECE 740

2. AGENDA Logistics Review from last lecture Caches 2

3. LOGISTICS Milestone II Meetings – Today Review class – Problem solving class – Tuesday April 19 3

4. TWO-LEVEL PREDICTOR Intuition behind two-level predictors Realization 1: A branch’s outcome can be correlated with other branches’ outcomes – Global branch correlation Realization 2: A branch’s outcome can be correlated with past outcomes of the same branch (other than the outcome of the branch “last-time” it was executed) – Local branch correlation 4

5. target address ONE-LEVEL BRANCH PREDICTOR Direction predictor (2-bit counters) Cache of Target Addresses (BTB: Branch Target Buffer) Program Counter PC + inst size taken? Next Fetch Address hit? Address of the current instruction 5

6. target address TWO-LEVEL GLOBAL HISTORY PREDICTOR Direction predictor (2-bit counters) Cache of Target Addresses (BTB: Branch Target Buffer) Program Counter Global branch history PC + inst size taken? Next Fetch Address hit? Which direction earlier branches went Address of the current instruction 6

7. target address TWO-LEVEL GSHARE PREDICTOR Direction predictor (2-bit counters) Cache of Target Addresses (BTB: Branch Target Buffer) Program Counter Global branch history XOR PC + inst size taken? Next Fetch Address hit? Which direction earlier branches went Address of the current instruction 7

8. target address TWO-LEVEL LOCAL HISTORY PREDICTOR Direction predictor (2-bit counters) Cache of Target Addresses (BTB: Branch Target Buffer) Program Counter PC + inst size taken? Next Fetch Address hit? Address of the current instruction Which directions earlier instances of *this branch* went 8

9. SOME OTHER BRANCH PREDICTOR TYPES Loop branch detector and predictor – Loop iteration count detector/predictor – Works well for loops, where iteration count is predictable – Used in Intel Pentium M Perceptron branch predictor – Learns the direction correlations between individual branches – Assigns weights to correlations – Jimenez and Lin, “Dynamic Branch Prediction with Perceptrons,” HPCA 2001. Hybrid history length based predictor – Uses different tables with different history lengths – Seznec, “Analysis of the O-Geometric History Length branch predictor,” ISCA 2005. 9

10. STATE OF THE ART IN BRANCH PREDICTION See the Branch Prediction Championship – http://www.jilp.org/cbp2014/program.html http://www.jilp.org/cbp2014/program.html 10 Andre Seznec, “TAGE-SC-L branch predictors,” CBP 2014.

11. CACHING BASICS 11

12. REVIEW: DIRECT-MAPPED CACHE STRUCTURE Assume byte-addressable memory: 256 bytes, 8- byte blocks  32 blocks Assume cache: 64 bytes, 8 blocks – Direct-mapped: A block can go to only one location – Addresses with same index contend for the same location  Causes conflict misses 12 Tag store Data store Address tag indexbyte in block 3 bits 2b V tag =? MUX byte in block Hit?Data

13. REVIEW: PROBLEM WITH DIRECT-MAPPED Direct-mapped cache: Two blocks in memory that map to the same index in the cache cannot be present in the cache at the same time – One index  one entry Can lead to 0% hit rate if more than one block accessed in an interleaved manner map to the same index – Assume addresses A and B have the same index bits but different tag bits – A, B, A, B, A, B, A, B, …  conflict in the cache index – All accesses are conflict misses 13

14. REVIEW: SET ASSOCIATIVITY Addresses 0 and 8 always conflict in direct mapped cache Instead of having one column of 8, have 2 columns of 4 blocks 14 Tag storeData store V tag =? V tag =? Address tag indexbyte in block 3 bits 2 bits 3b Logic MUX byte in block Associative memory within the set -- More complex, slower access, larger tag store + Accommodates conflicts better (fewer conflict misses) SET Hit?

15. REVIEW: HIGHER ASSOCIATIVITY 4-way -- More tag comparators and wider data mux; larger tags + Likelihood of conflict misses even lower 15 Tag store Data store =? MUX byte in block Logic Hit?

16. REVIEW: FULL ASSOCIATIVITY Fully associative cache – A block can be placed in any cache location 16 Tag store Data store =? MUX byte in block Logic Hit?

17. REVIEW: APPROXIMATIONS OF LRU Most modern processors do not implement “true LRU” in highly-associative caches Why? – True LRU is complex – LRU is an approximation to predict locality anyway (i.e., not the best possible replacement policy) Examples: – Not MRU (not most recently used) – Hierarchical LRU: divide the 4-way set into 2-way “groups”, track the MRU group and the MRU way in each group – Victim-NextVictim Replacement: Only keep track of the victim and the next victim 17

18. REPLACEMENT POLICY LRU vs. Random – Set thrashing: When the “program working set” in a set is larger than set associativity – 4-way: Cyclic references to A, B, C, D, E 0% hit rate with LRU policy – Random replacement policy is better when thrashing occurs In practice: – Depends on workload – Average hit rate of LRU and Random are similar Hybrid of LRU and Random – How to choose between the two? Set sampling See Qureshi et al., “A Case for MLP-Aware Cache Replacement,“ ISCA 2006. 18

19. OPTIMAL REPLACEMENT POLICY? Belady’s OPT – Replace the block that is going to be referenced furthest in the future by the program – Belady, “A study of replacement algorithms for a virtual- storage computer,” IBM Systems Journal, 1966. – How do we implement this? Simulate? Is this optimal for minimizing miss rate? Is this optimal for minimizing execution time? – No. Cache miss latency/cost varies from block to block! – Two reasons: Remote vs. local caches and miss overlapping – Qureshi et al. “A Case for MLP-Aware Cache Replacement,“ ISCA 2006. 19

20. HANDLING WRITES (STORES) When do we write the modified data in a cache to the next level? Write through: At the time the write happens Write back: When the block is evicted – Write-back + Can consolidate multiple writes to the same block before eviction – Potentially saves bandwidth between cache levels + saves energy -- Need a bit in the tag store indicating the block is “modified” – Write-through + Simpler + All levels are up to date. Consistency: Simpler cache coherence because no need to check lower-level caches -- More bandwidth intensive; no coalescing of writes 20

21. HANDLING WRITES (STORES) Do we allocate a cache block on a write miss? – Allocate on write miss: Yes – No-allocate on write miss: No Allocate on write miss + Can consolidate writes instead of writing each of them individually to next level + Simpler because write misses can be treated the same way as read misses -- Requires (?) transfer of the whole cache block No-allocate + Conserves cache space if locality of writes is low (potentially better cache hit rate) 21

22. CACHE PARAMETERS VS. MISS RATE Cache size Block size Associativity Replacement policy Insertion/Placement policy 22

23. CACHE SIZE Cache size: total data (not including tag) capacity – bigger can exploit temporal locality better – not ALWAYS better Too large a cache adversely affects hit and miss latency – smaller is faster => bigger is slower – access time may degrade critical path Too small a cache – doesn’t exploit temporal locality well – useful data replaced often Working set: the whole set of data the executing application references – Within a time interval 23 hit rate cache size “working set” size

24. BLOCK SIZE Block size is the data that is associated with an address tag – not necessarily the unit of transfer between hierarchies Sub-blocking: A block divided into multiple pieces (each with V bit) – Can improve “write” performance Too small blocks – don’t exploit spatial locality well – have larger tag overhead Too large blocks – too few total # of blocks likely-useless data transferred Extra bandwidth/energy consumed 24 hit rate block size

25. LARGE BLOCKS: CRITICAL-WORD AND SUBBLOCKING Large cache blocks can take a long time to fill into the cache – fill cache line critical word first – restart cache access before complete fill Large cache blocks can waste bus bandwidth – divide a block into subblocks – associate separate valid bits for each subblock – When is this useful? 25 tag subblockv v vddd

26. ASSOCIATIVITY How many blocks can map to the same index (or set)? Larger associativity – lower miss rate, less variation among programs – diminishing returns, higher hit latency Smaller associativity – lower cost – lower hit latency Especially important for L1 caches Power of 2 associativity? 26 associativity hit rate

27. CLASSIFICATION OF CACHE MISSES Compulsory miss – first reference to an address (block) always results in a miss – subsequent references should hit unless the cache block is displaced for the reasons below – dominates when locality is poor Capacity miss – cache is too small to hold everything needed – defined as the misses that would occur even in a fully- associative cache (with optimal replacement) of the same capacity Conflict miss – defined as any miss that is neither a compulsory nor a capacity miss 27

28. HOW TO REDUCE EACH MISS TYPE Compulsory – Caching cannot help – Prefetching Conflict – More associativity – Other ways to get more associativity without making the cache associative Victim cache Hashing Software hints? Capacity – Utilize cache space better: keep blocks that will be referenced – Software management: divide working set such that each “phase” fits in cache 28

29. IMPROVING CACHE “PERFORMANCE” Remember – Average memory access time (AMAT) = ( hit-rate * hit-latency ) + ( miss-rate * miss-latency ) Reducing miss rate – Caveat: reducing miss rate can reduce performance if more costly-to-refetch blocks are evicted Reducing miss latency/cost Reducing hit latency 29

30. IMPROVING BASIC CACHE PERFORMANCE Reducing miss rate – More associativity – Alternatives/enhancements to associativity Victim caches, hashing, pseudo-associativity, skewed associativity – Better replacement/insertion policies – Software approaches Reducing miss latency/cost – Multi-level caches – Critical word first – Subblocking/sectoring – Better replacement/insertion policies – Non-blocking caches (multiple cache misses in parallel) – Multiple accesses per cycle – Software approaches 30

31. VICTIM CACHE: REDUCING CONFLICT MISSES Jouppi, “Improving Direct-Mapped Cache Performance by the Addition of a Small Fully-Associative Cache and Prefetch Buffers,” ISCA 1990. Idea: Use a small fully associative buffer (victim cache) to store evicted blocks + Can avoid ping ponging of cache blocks mapped to the same set (if two cache blocks continuously accessed in nearby time conflict with each other) -- Increases miss latency if accessed serially with L2 31 Direct Mapped Cache Next Level Cache Victim cache

32. HASHING AND PSEUDO-ASSOCIATIVITY Hashing: Better “randomizing” index functions + can reduce conflict misses by distributing the accessed memory blocks more evenly to sets – Example: stride where stride value equals cache size -- More complex to implement: can lengthen critical path Pseudo-associativity (Poor Man’s associative cache) + can reduce conflict miss – Serial lookup: On a miss, use a different index function and access cache again +/- Introduces heterogeneity in hit latency 32

33. SKEWED ASSOCIATIVE CACHES (I) Basic 2-way associative cache structure 33 Way 0 Way 1 Tag Index Byte in Block Same index function for each way =?

34. Skewed associative caches – Each bank has a different index function 34 Way 0Way 1 tag index byte in block f0 same index same set same index redistributed to different sets =? SKEWED ASSOCIATIVE CACHES (II)

35. Idea: Reduce conflict misses by using different index functions for each cache way Benefit: indices are randomized – Less likely two blocks have same index Reduced conflict misses – May be able to reduce associativity Cost: additional latency of hash function Seznec, “A Case for Two-Way Skewed-Associative Caches,” ISCA 1993. 35 SKEWED ASSOCIATIVE CACHES (III)

36. IMPROVING BASIC CACHE PERFORMANCE Reducing miss rate – More associativity – Alternatives/enhancements to associativity Victim caches, hashing, pseudo-associativity, skewed associativity – Better replacement/insertion policies – Software approaches Reducing miss latency/cost – Multi-level caches – Critical word first – Subblocking/sectoring – Better replacement/insertion policies – Non-blocking caches (multiple cache misses in parallel) – Multiple accesses per cycle – Software approaches 36

37. MLP-AWARE CACHE REPLACEMENT Moinuddin K. Qureshi, Daniel N. Lynch, Onur Mutlu, and Yale N. Patt, "A Case for MLP-Aware Cache Replacement" Proceedings of the 33rd International Symposium on Computer Architecture (ISCA), pages 167-177, Boston, MA, June 2006. Slides (ppt) "A Case for MLP-Aware Cache Replacement"33rd International Symposium on Computer ArchitectureSlides (ppt) 37

38. 38 Memory Level Parallelism (MLP)  Memory Level Parallelism (MLP) means generating and servicing multiple memory accesses in parallel [Glew’98]  Several techniques to improve MLP (e.g., out-of-order execution, runahead execution)  MLP varies. Some misses are isolated and some parallel How does this affect cache replacement? time A B C isolated miss parallel miss

39. Traditional Cache Replacement Policies  Traditional cache replacement policies try to reduce miss count  Implicit assumption: Reducing miss count reduces memory-related stall time  Misses with varying cost/MLP breaks this assumption!  Eliminating an isolated miss helps performance more than eliminating a parallel miss  Eliminating a higher-latency miss could help performance more than eliminating a lower-latency miss 39

40. 40 Misses to blocks P1, P2, P3, P4 can be parallel Misses to blocks S1, S2, and S3 are isolated Two replacement algorithms: 1.Minimizes miss count (Belady’s OPT) 2.Reduces isolated misses (MLP-Aware) For a fully associative cache containing 4 blocks S1 P4 P3 P2 P1 P1 P2 P3 P4 S2S3 An Example

41. Fewest Misses = Best Performance 41 P3P2P1P4 H H MH H H MHit/Miss Misses=4 Stalls=4 S1 P4 P3 P2 P1 P1 P2 P3 P4 S2S3 Time stall Belady’s OPT replacement MM MLP-Aware replacement Hit/Miss P3P2S1P4P3P2P1P4P3P2S2P4P3P2S3P4S1S2S3P1P3P2S3P4S1S2S3P4 H H H S1S2S3P4 H M M M Time stall Misses=6 Stalls=2 Saved cycles Cache

42. 42 Motivation  MLP varies. Some misses more costly than others  MLP-aware replacement can improve performance by reducing costly misses

43. 43 Outline  Introduction  MLP-Aware Cache Replacement  Model for Computing Cost  Repeatability of Cost  A Cost-Sensitive Replacement Policy  Practical Hybrid Replacement  Tournament Selection  Dynamic Set Sampling  Sampling Based Adaptive Replacement  Summary

44. 44 Computing MLP-Based Cost  Cost of miss is number of cycles the miss stalls the processor  Easy to compute for isolated miss  Divide each stall cycle equally among all parallel misses A B C t0 t1 t4t5 time 1 ½ 1½ ½ t2 t3 ½ 1

45. 45  Miss Status Holding Register (MSHR) tracks all in flight misses  Add a field mlp-cost to each MSHR entry  Every cycle for each demand entry in MSHR mlp-cost += (1/N) N = Number of demand misses in MSHR A First-Order Model

46. 46 Machine Configuration  Processor  aggressive, out-of-order, 128-entry instruction window  L2 Cache  1MB, 16-way, LRU replacement, 32 entry MSHR  Memory  400 cycle bank access, 32 banks  Bus  Roundtrip delay of 11 bus cycles (44 processor cycles)

47. 47 Distribution of MLP-Based Cost Cost varies. Does it repeat for a given cache block? MLP-Based Cost % of All L2 Misses

48. 48 Repeatability of Cost  An isolated miss can be parallel miss next time  Can current cost be used to estimate future cost ?  Let  = difference in cost for successive miss to a block  Small   cost repeats  Large   cost varies significantly

49. 49  In general  is small  repeatable cost  When  is large (e.g. parser, mgrid)  performance loss Repeatability of Cost  < 60  < 120   120

50. 50 The Framework MSHR L2 CACHE MEMORY Quantization of Cost Computed mlp-based cost is quantized to a 3-bit value CCL CARECARE Cost-Aware Repl Engine Cost Calculation Logic PROCESSOR ICACHEDCACHE

51. 51  A Linear (LIN) function that considers recency and cost Victim-LIN = min { Recency (i) + S*cost (i) } S = significance of cost. Recency(i) = position in LRU stack cost(i) = quantized cost Design of MLP-Aware Replacement policy  LRU considers only recency and no cost Victim-LRU = min { Recency (i) }  Decisions based only on cost and no recency hurt performance. Cache stores useless high cost blocks

52. 52 Results for the LIN policy Performance loss for parser and mgrid due to large .

53. 53 Effect of LIN policy on Cost Miss += 4% IPC += 4% Miss += 30% IPC -= 33% Miss -= 11% IPC += 22%

54. 54 Outline  Introduction  MLP-Aware Cache Replacement  Model for Computing Cost  Repeatability of Cost  A Cost-Sensitive Replacement Policy  Practical Hybrid Replacement  Tournament Selection  Dynamic Set Sampling  Sampling Based Adaptive Replacement  Summary

55. 55 Tournament Selection (TSEL) of Replacement Policies for a Single Set ATD-LINATD-LRU Saturating Counter (SCTR) HIT Unchanged MISS Unchanged HITMISS+= Cost of Miss in ATD-LRU MISSHIT-= Cost of Miss in ATD-LIN SET A + SCTR If MSB of SCTR is 1, MTD uses LIN else MTD use LRU ATD-LIN ATD-LRU SET A MTD

56. 56 Extending TSEL to All Sets Implementing TSEL on a per-set basis is expensive Counter overhead can be reduced by using a global counter + SCTR Policy for All Sets In MTD Set A ATD-LIN Set B Set C Set D Set E Set F Set G Set H Set A ATD-LRU Set B Set C Set D Set E Set F Set G Set H

57. 57 Dynamic Set Sampling + SCTR Policy for All Sets In MTD ATD-LIN Set B Set E Set G Set B Set E Set G ATD-LRU Set A Set C Set D Set F Set H Set C Set D Set F Set H Not all sets are required to decide the best policy Have the ATD entries only for few sets. Sets that have ATD entries (B, E, G) are called leader sets

58. 58 Dynamic Set Sampling  Bounds using analytical model and simulation (in paper)  DSS with 32 leader sets performs similar to having all sets  Last-level cache typically contains 1000s of sets, thus ATD entries are required for only 2%-3% of the sets How many sets are required to choose best performing policy? ATD overhead can further be reduced by using MTD to always simulate one of the policies (say LIN)

59. 59 Decide policy only for follower sets + Sampling Based Adaptive Replacement (SBAR) The storage overhead of SBAR is less than 2KB (0.2% of the baseline 1MB cache) SCTR MTD Set B Set E Set G ATD-LRU Set A Set C Set D Set F Set H Set B Set E Leader sets Follower sets

60. 60 Results for SBAR

61. 61 SBAR adaptation to phases SBAR selects the best policy for each phase of ammp LIN is better LRU is better

62. 62 Outline  Introduction  MLP-Aware Cache Replacement  Model for Computing Cost  Repeatability of Cost  A Cost-Sensitive Replacement Policy  Practical Hybrid Replacement  Tournament Selection  Dynamic Set Sampling  Sampling Based Adaptive Replacement  Summary

63. 63 Summary  MLP varies. Some misses are more costly than others  MLP-aware cache replacement can reduce costly misses  Proposed a runtime mechanism to compute MLP-Based cost and the LIN policy for MLP-aware cache replacement  SBAR allows dynamic selection between LIN and LRU with low hardware overhead  Dynamic set sampling used in SBAR also enables other cache related optimizations

64. Samira Khan University of Virginia Apr 14, 2016 COMPUTER ARCHITECTURE CS 6354 Caches The content and concept of this course are adapted from CMU ECE 740