1 / 40

AKT211 – CAO 09 – Cache

AKT211 – CAO 09 – Cache. Ghifar Parahyangan Catholic University Nov 7, 2011. Last Course Review. Error Correction in RAM. Outline. Cache Memory Principles Basic Positioning Cache vs Main Memory Structure Elements of Cache Design Addressing Size Mapping Function Direct Mapping

caleb-kim
Download Presentation

AKT211 – CAO 09 – Cache

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. AKT211 – CAO09 – Cache Ghifar Parahyangan Catholic University Nov 7, 2011

  2. Last Course Review • Error Correction in RAM

  3. Outline • Cache Memory Principles • Basic • Positioning • Cache vs Main Memory Structure • Elements of Cache Design • Addressing • Size • Mapping Function • Direct Mapping • Associative Memory • Set Associative

  4. CACHE MEMORY PRINCIPLES

  5. Cache Basic • Small amount of fast memory • Sits between normal main memory and CPU • May be located on CPU chip or module

  6. Cache Positioning

  7. Cache vs Main Memory Structure

  8. Cache Operation - overview • CPU requests contents of memory location • Check cache for this data • If present, get from cache (fast) • If not present, read required block from main memory to cache • Then deliver from cache to CPU • Cache includes tags to identify which block of main memory is in each cache slot

  9. Cache Read Operation - Flowchart

  10. ELEMENTS OF CACHE DESIGN

  11. Cache Design • Addressing • Size • Mapping Function • Replacement Algorithm • Write Policy • Block Size • Number of Caches

  12. Cache Addressing • Nowadays, almost all architectures supports virtual memory • So, where does cache sit? • Between processor and virtual Memory Management Unit (MMU) – Logical Cache • Between MMU and main memory – Physical Cache • Logical cache (virtual cache) stores data using virtual addresses • Processor accesses cache directly, not thorough physical cache • Cache access faster, before MMU address translation • Virtual addresses use same address space for different applications • Must flush cache on each context switch • Physical cache stores data using main memory physical addresses

  13. Cache Addressing (2)

  14. Cache Size • Cost • More cache is expensive • Speed • More cache is faster (up to a point) • Checking cache for data takes time

  15. Comparison of Cache Size

  16. MAPPING FUNCTION

  17. Mapping Function • Cache Lines << Main Memory Blocks • Cache of 64kByte • Cache block of 4 bytes • i.e. cache is 16k (214) lines of 4 bytes • 16MBytes main memory • 24 bit address (224=16M) • Which main memory block currently occupies a cache line? • The choice of mapping function dictates how the cache is organized • 3 techniques can be used : direct, associative, set associative

  18. Direct • Each block of main memory maps to only one cache line • i.e. if a block is in cache, it must be in one specific place

  19. Direct Mapping Address Structure • 24 bit address • 2 bit word identifier (4 byte block) • 22 bit block identifier • 8 bit tag (=22-14) • 14 bit slot or line • No two blocks in the same line have the same Tag field • Check contents of cache by finding line and checking Tag Tag s-r Line or Slot r Word w 14 2 8

  20. Direct Mapping from Cache to Main Memory

  21. Direct Mapping Cache Organization

  22. Direct MappingExample

  23. Direct Mapping Summary • Address length = (s + w) bits • Number of addressable units = 2s+w words or bytes • Block size = line size = 2w words or bytes • Number of blocks in main memory = • 2s+ w/2w = 2s • Number of lines in cache = m = 2r • Size of tag = (s – r) bits

  24. Direct Mapping pros & cons • Pros : • Simple& Inexpensive • Cons • Fixed location for given block • If a program accesses 2 blocks that map to the same line repeatedly, cache misses are very high

  25. Associative Mapping • A main memory block can load into any line of cache • Memory address is interpreted as tag and word • Tag uniquely identifies block of memory • Every line’s tag is examined for a match • Cache searching gets expensive

  26. Associative Mapping Address Structure • 22 bit tag stored with each 32 bit block of data • Compare tag field with tag entry in cache to check for hit • Least significant 2 bits of address identify which 16 bit word is required from 32 bit data block • e.g. Tag 22 bit Word 2 bit

  27. Associative Mapping from Cache to Main Memory

  28. Fully Associative Cache Organization

  29. Associative Mapping Example

  30. Associative Mapping Summary • Address length = (s + w) bits • Number of addressable units = 2s+w words or bytes • Block size = line size = 2w words or bytes • Number of blocks in main memory = 2s+ w/2w = 2s • Number of lines in cache = undetermined • Size of tag = s bits

  31. Set Associative Mapping • Cache is divided into a number of sets • Each set contains a number of lines • A given block maps to any line in a given set • e.g. Block B can be in any line of set i • e.g. 2 lines per set • 2 way associative mapping • A given block can be in one of 2 lines in only one set

  32. Mapping From Main Memory to Cache:v Associative

  33. K-Way Set Associative Cache Organization

  34. Word 2 bit Tag 9 bit Set 13 bit Set Associative MappingAddress Structure • Use set field to determine cache set to look in • Compare tag field to see if we have a hit

  35. Two Way Set Associative Mapping Example

  36. Set Associative Mapping Summary • Address length = (s + w) bits • Number of addressable units = 2s+w words or bytes • Block size = line size = 2w words or bytes • Number of blocks in main memory = 2s+w /2w= 2s • Number of lines in set = k • Number of sets = v = 2d • Number of lines in cache = kv = k *2d • Size of tag = (s – d) bits

  37. Set Associative Mapping Summary (2) • In extreme case : • If v = m and k=1 direct mapping • If v = 1 and k=m  direct mapping • The use of two lines per set (v = m/2, k=2) is the most common set-associative organization

  38. Associativity Simulation Result

  39. ANY QUESTION ?

  40. THANK YOU

More Related