0% found this document useful (0 votes)
51 views56 pages

13 Memory

The document discusses memory hierarchy and caches. It explains that caches use faster SRAM memory while main memory uses larger but slower DRAM memory. It describes the need for cache memory to bridge the speed gap between the processor and main memory. It provides details on SRAM and DRAM cell designs and explains concepts like memory modules, burst mode operations, and synchronous DRAM technologies like SDRAM and DDR SDRAM.

Uploaded by

max scalom
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
51 views56 pages

13 Memory

The document discusses memory hierarchy and caches. It explains that caches use faster SRAM memory while main memory uses larger but slower DRAM memory. It describes the need for cache memory to bridge the speed gap between the processor and main memory. It provides details on SRAM and DRAM cell designs and explains concepts like memory modules, burst mode operations, and synchronous DRAM technologies like SDRAM and DDR SDRAM.

Uploaded by

max scalom
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 56

Memory Hierarchy and Caches

COE 301 / ICS 233


Computer Organization
Dr. Muhamed Mudawar
College of Computer Sciences and Engineering
King Fahd University of Petroleum and Minerals
Presentation Outline

 Random Access Memory and its Structure

 Memory Hierarchy and the need for Cache Memory

 The Basics of Caches

 Cache Performance and Memory Stall Cycles

 Improving Cache Performance

 Multilevel Caches

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 2
Memory Technology
 Static RAM (SRAM)
 Used typically to implement Cache memory

 Requires 6 transistors per bit


 Low power to retain bit

 Dynamic RAM (DRAM)


 Used typically to implement Main Memory

 One transistor + capacitor per bit


 Must be re-written after being read
 Must be refreshed periodically
 By reading and rewriting all the rows in the DRAM

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 3
Static RAM Storage Cell
Word line
 Static RAM (SRAM) Memory
Vcc

 Typically used for caches

 Provides fast access time

 Cell Implementation: bit bit

Typical SRAM cell


 6-Transistor cell
Word line
 Cross-coupled inverters store bit

 Two pass transistors

 Row decoder selects the word line bit bit

 Pass transistors enable the cell to be read and written


Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 4
Dynamic RAM Storage Cell
 Dynamic RAM (DRAM): cheap, dense, but slower than SRAM
 Typical choice for main memory Word line

 Cell Implementation:
Pass
 1-Transistor cell (pass transistor) Transistor

 Trench capacitor (stores bit) Capacitor

 Bit is stored as a charge on capacitor bit

 Must be refreshed periodically Typical DRAM cell

 Because of leakage of charge from tiny capacitor

 Refreshing for all memory rows


 Reading each row and writing it back to restore the charge

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 5
Example of a Memory Chip
 24-pin dual in-line package: 222  4-bit = 16Mibit memory

 22-bit address is divided into Legend


Ai Address bit i
 11-bit row address CAS Column address strobe
Dj Data bit j
NC No connection
 11-bit column address OE Output enable
RAS Row address strobe
WE Write enable
 Interleaved on same address lines

Vss D4 D3 CAS OE A9 A8 A7 A6 A5 A4 Vss

24 23 22 21 20 19 18 17 16 15 14 13

1 2 3 4 5 6 7 8 9 10 11 12

Vcc D1 D2 WE RAS NC A10 A0 A1 A2 A3 Vcc

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 6
Typical Memory Structure
 Row decoder
 Select row to read/write

Row Decoder
Row address
 Column decoder r 2r × 2c × m bits

...
 Select column to read/write Cell Matrix

 Cell Matrix
 2D array of tiny memory cells Sense/write amplifiers
m
Data Row Latch 2c × m bits
 Sense/Write amplifiers
...
 Sense & amplify data on read
Column Decoder
 Drive bit line with data in on write c

Column address
 Same data lines are used for data in/out

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 7
DRAM Operation
 Row Access (RAS)
 Latch and decode row address to enable addressed row
 Small change in voltage detected by sense amplifiers
 Latch whole row of bits
 Sense amplifiers drive bit lines to recharge storage cells

 Column Access (CAS) read and write operation


 Latch and decode column address to select m bits
 m = 4, 8, 16, or 32 bits depending on the DRAM package
 On read, send latched bits out to chip pins
 On write, charge storage cells to required value
 Can perform multiple column accesses to same row (burst mode)
Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 8
Burst Mode Operation
 Used for Block Transfer
 Row address is latched and decoded

 A read operation causes ALL cells in a selected row to be read

 Selected row is latched internally inside the DRAM chip

 Column address is latched and decoded

 Selected column data is placed in the data output register

 Column address is incremented automatically

 Multiple data items are read depending on the block length

 Fast transfer of blocks between main memory and cache

 Fast transfer of pages between main memory and disk

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 9
SDRAM and DDR SDRAM
 SDRAM is Synchronous Dynamic RAM
 Added clock to DRAM interface

 SDRAM is synchronous with the system clock


 Older DRAM technologies were asynchronous
 As system bus clock improved, SDRAM delivered higher
performance than asynchronous DRAM

 DDR is Double Data Rate SDRAM


 Like SDRAM, DDR is synchronous with the system clock,
but the difference is that DDR reads data on both the
rising and falling edges of the clock signal
Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 10
Memory Modules
 Memory Rank: Set of DRAM chips accessed in parallel
 Same Chip Select (CS) and Command (CMD)

 Same address, but different data lines

 Increases memory capacity and bandwidth

 Example: 64-bit data bus using 4 × 16-bit DRAM chips

CLK CS CMD CLK CS CMD CLK CS CMD

Address Address ... Address

Data Data Data


m m
..

Data width = p × m bits


Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 11
Trends in DRAM
Chip Bus Data Peak Total latency to
Memory
Year Capacity Clock Rate Bandwidth a new
Standard
(Mibit) (MHz) (MT/s) (MB/s) row / column

1996 SDRAM 64-128 100-166 100-166 800-1333 60 ns


2000 DDR 256-512 100-200 200-400 1600-3200 55 ns
2004 DDR2 512-2048 200-400 400-800 3200-6400 50 ns
2010 DDR3 2048-8192 400-800 800-1600 6400-12800 40 ns
2014 DDR4 8192-32768 800-1600 1600-3200 12800-25600 35 ns

 Memory chip capacity: 1 Mibit = 220 bits, 1 Gibit = 230 bits


 Data Rate = Millions of Transfers per second (MT/s)
 Data Rate = 2 × Bus Clock for DDR, DDR2, DDR3, DDR4
 1 Transfer = 8 bytes of data  Bandwidth = MT/s × 8 bytes
Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 12
Memory Latency versus Bandwidth
 Memory Latency
 Elapsed time between sending address and receiving data
 Measured in nanoseconds
 The total latency to a new row/column is the time between opening a new
row of memory and accessing a column within it.
 Reduced from 60 ns to 35 ns (between 1996 and 2016)
 Improvement in memory latency is less than 2X (1996 to 2016)

 Memory Bandwidth
 Rate at which data is transferred between memory and CPU
 Bandwidth is measured as millions of Bytes per second
 Increased from 800 to 25600 MBytes/sec (between 1996 and 2016)
 Improvement in memory bandwidth is 32X (1996 to 2016)

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 13
DRAM Refresh Cycles
 Refresh cycle is about tens of milliseconds
 Refreshing is done for the entire memory
 Each row is read and written back to restore the charge
 Some of the memory bandwidth is lost to refresh cycles

Voltage 1 Written Refreshed Refreshed Refreshed


for 1

Threshold
voltage

0 Stored Refresh Cycle


Voltage Time
for 0

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 14
Next . . .

 Random Access Memory and its Structure

 Memory Hierarchy and the need for Cache Memory

 The Basics of Caches

 Cache Performance and Memory Stall Cycles

 Improving Cache Performance

 Multilevel Caches

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 15
Processor-Memory Performance Gap

CPU Performance: 55% per year,


slowing down after 2004

Performance Gap
DRAM: 7% per year

 1980 – No cache in microprocessor


 1995 – Two-level cache on microprocessor
Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 16
The Need for Cache Memory
 Widening speed gap between CPU and main memory
 Processor operation takes less than 1 ns

 Main memory requires more than 50 ns to access

 Each instruction involves at least one memory access


 One memory access to fetch the instruction

 A second memory access for load and store instructions

 Memory bandwidth limits the instruction execution rate

 Cache memory can help bridge the CPU-memory gap

 Cache memory is small in size but fast

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 17
Typical Memory Hierarchy
 Registers are at the top of the hierarchy
 Typical size < 1 KB
 Access time < 0.5 ns
Microprocessor
 Level 1 Cache (8 – 64 KiB) Registers
 Access time: 1 ns
L1 Cache
 L2 Cache (1 MiB – 8 MiB) L2 Cache

Bigger
Faster
 Access time: 3 – 10 ns
Memory Bus
 Main Memory (8 – 32 GiB) Main Memory
 Access time: 40 – 50 ns I/O Bus

 Disk Storage (> 200 GB) Magnetic or Flash Disk

 Access time: 5 – 10 ms

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 18
Principle of Locality of Reference
 Programs access small portion of their address space
 At any time, only a small set of instructions & data is needed

 Temporal Locality (in time)


 If an item is accessed, probably it will be accessed again soon
 Same loop instructions are fetched each iteration
 Same procedure may be called and executed many times

 Spatial Locality (in space)


 Tendency to access contiguous instructions/data in memory
 Sequential execution of Instructions
 Traversing arrays element by element

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 19
What is a Cache Memory ?
 Small and fast (SRAM) memory technology
 Stores the subset of instructions & data currently being accessed

 Used to reduce average access time to memory


 Caches exploit temporal locality by …
 Keeping recently accessed data closer to the processor

 Caches exploit spatial locality by …


 Moving blocks consisting of multiple contiguous words

 Goal is to achieve
 Fast speed of cache memory access
 Balance the cost of the memory system

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 20
Cache Memories in the Datapath
Imm16

Imm
Ext
ALU result 32
0
32
1

A
I-Cache D-Cache

Register File
Rs 5 BusA 2
A
Instruction
0
RA 3
L

Data
R
0 Address
Instruction Rt 5
RB BusB 0 U Data_out
32
PC

1 Address 1 1 1

B
2 2 0
Data_in

D
RW BusW
3 32
32
0

Rd4
Rd2

Rd3
1
Rd

clk
Instruction Block
Block Address

Block Address

D-Cache miss
I-Cache miss

I-Cache miss or D-Cache miss causes

Data Block
pipeline to stall

Interface to L2 Cache or Main Memory

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 21
Almost Everything is a Cache !
 In computer architecture, almost everything is a cache!

 Registers: a cache on variables – software managed

 First-level cache: a cache on second-level cache

 Second-level cache: a cache on memory (or L3 cache)

 Memory: a cache on hard disk


 Stores recent programs and their data

 Hard disk can be viewed as an extension to main memory

 Branch target and prediction buffer


 Cache on branch target and prediction information

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 22
Next . . .

 Random Access Memory and its Structure

 Memory Hierarchy and the need for Cache Memory

 The Basics of Caches

 Cache Performance and Memory Stall Cycles

 Improving Cache Performance

 Multilevel Caches

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 23
Four Basic Questions on Caches
 Q1: Where can a block be placed in a cache?
 Block placement
 Direct Mapped, Set Associative, Fully Associative
 Q2: How is a block found in a cache?
 Block identification
 Block address, tag, index
 Q3: Which block should be replaced on a cache miss?
 Block replacement
 FIFO, Random, LRU
 Q4: What happens on a write?
 Write strategy
 Write Back or Write Through cache (with Write Buffer)

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 24
Inside a Cache Memory
Address Address
Cache Main
Processor Data Data
Memory Memory

N Cache Blocks
Tags Address Tag 0 Cache Block 0

identify Address Tag 1 Cache Block 1

blocks in ... ...


the cache Tag N – 1 Cache Block N – 1

 Cache Block (or Cache Line)


 Unit of data transfer between main memory and a cache
 Large block size  Less tag overhead + Burst transfer from DRAM
 Typically, cache block size = 64 bytes in recent caches

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 25
Block Placement: Direct Mapped
 Block: unit of data transfer between cache and memory
 Direct Mapped Cache:
 A block can be placed in exactly one location in the cache

000
001
010

100
101
011

110
111
In this example:

Cache
Cache index =
least significant 3 bits of
Block address

Memory
Main
00000
00001
00010

00100
00101

01000
01001
01010

10000
10001
10010

10100
10101
10110

11000
11001
11010
00011

00110

01011
01100
01101

10011

10111

11011
11100
11101
00111

01110

11110
01111

11111
Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 26
Direct-Mapped Cache
 A memory address is divided into
Block Address
 Block address: identifies block in memory
Tag Index offset
 Block offset: to access bytes within a block

 A block address is further divided into V Tag Block Data

 Index: used for direct cache access


 Tag: most-significant bits of block address
Index = Block Address mod Cache Blocks

 Tag must be stored also inside cache


 For block identification =

 A valid bit is also required to indicate Data

Hit
 Whether a cache block is valid or not

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 27
Direct Mapped Cache – cont’d
 Cache hit: block is stored inside cache
 Index is used to access cache block Block Address

 Address tag is compared against stored tag Tag Index offset

 If equal and cache block is valid then hit


 Otherwise: cache miss V Tag Block Data

 If number of cache blocks is 2n


 n bits are used for the cache index
 If number of bytes in a block is 2b
 b bits are used for the block offset
 If 32 bits are used for an address =
 32 – n – b bits are used for the tag Data

 Cache data size = 2n+b bytes Hit

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 28
Mapping an Address to a Cache Block
 Example
 Consider a direct-mapped cache with 256 blocks
 Block size = 16 bytes
 Compute tag, index, and byte offset of address: 0x01FFF8AC

 Solution Block Address

20 8 4
 32-bit address is divided into: Tag Index offset

 4-bit byte offset field, because block size = 24 = 16 bytes


 8-bit cache index, because there are 28 = 256 blocks in cache
 20-bit tag field
 Byte offset = 0xC = 12 (least significant 4 bits of address)
 Cache index = 0x8A = 138 (next lower 8 bits of address)
 Tag = 0x01FFF (upper 20 bits of address)

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 29
Example on Cache Placement & Misses
 Consider a small direct-mapped cache with 32 blocks
 Cache is initially empty, Block size = 16 bytes
 The following memory addresses (in decimal) are referenced:
1000, 1004, 1008, 2548, 2552, 2556.
 Map addresses to cache blocks and indicate whether hit or miss
23 5 4
 Solution: Tag Index offset

 1000 = 0x3E8 cache index = 0x1E Miss (first access)


 1004 = 0x3EC cache index = 0x1E Hit
 1008 = 0x3F0 cache index = 0x1F Miss (first access)
 2548 = 0x9F4 cache index = 0x1F Miss (different tag)
 2552 = 0x9F8 cache index = 0x1F Hit
 2556 = 0x9FC cache index = 0x1F Hit
Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 30
Fully Associative Cache
 A block can be placed anywhere in cache  no indexing
 If m blocks exist then
 m comparators are needed to match tag
Address
 Cache data size = m  2b bytes
Tag offset

V Tag Block Data V Tag Block Data V Tag Block Data V Tag Block Data

= = = =

mux
m-way associative Data
Hit

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 31
Set-Associative Cache
 A set is a group of blocks that can be indexed
 A block is first mapped onto a set
 Set index = Block address mod Number of sets in cache

 If there are m blocks in a set (m-way set associative) then


 m tags are checked in parallel using m comparators

 If 2n sets exist then set index consists of n bits


 Cache data size = m  2n+b bytes (with 2b bytes per block)
 Without counting tags and valid bits

 A direct-mapped cache has one block per set (m = 1)


 A fully-associative cache has one set (2n = 1 or n = 0)

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 32
Set-Associative Cache Diagram
Address Tag Index offset

V Tag Block Data V Tag Block Data V Tag Block Data V Tag Block Data

= = = =

mux
m-way set-associative Hit
Data

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 33
Write Policy
 Write Through:
 Writes update cache and lower-level memory
 Cache control bit: only a Valid bit is needed
 Memory always has latest data, which simplifies data coherency
 Can always discard cached data when a block is replaced

 Write Back:
 Writes update cache only
 Cache control bits: Valid and Modified bits are required
 Modified cached data is written back to memory when replaced
 Multiple writes to a cache block require only one write to memory
 Uses less memory bandwidth than write-through and less power
 However, more complex to implement than write through

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 34
What Happens on a Cache Miss?
 Cache sends a miss signal to stall the processor
 Decide which cache block to allocate/replace
 One choice only when the cache is directly mapped
 Multiple choices for set-associative or fully-associative cache

 Transfer the block from lower level memory to this cache


 Set the valid bit and the tag field from the upper address bits

 If block to be replaced is modified then write it back


 Modified block is written back to memory
 Otherwise, block to be replaced can be simply discarded

 Restart the instruction that caused the cache miss


 Miss Penalty: clock cycles to process a cache miss

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 35
Replacement Policy
 Which block to be replaced on a cache miss?
 No selection alternatives for direct-mapped caches
 m blocks per set to choose from for associative caches
 Random replacement
 Candidate blocks are randomly selected
 One counter for all sets (0 to m – 1): incremented on every cycle
 On a cache miss replace block specified by counter

 First In First Out (FIFO) replacement


 Replace oldest block in set
 One counter per set (0 to m – 1): specifies oldest block to replace
 Counter is incremented on a cache miss

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 36
Replacement Policy – cont’d
 Least Recently Used (LRU)
 Replace block that has been unused for the longest time
 Order blocks within a set from least to most recently used
 Update ordering of blocks on each cache hit
 With m blocks per set, there are m! possible permutations

 Pure LRU is too costly to implement when m > 2


 m = 2, there are 2 permutations only (a single bit is needed)
 m = 4, there are 4! = 24 possible permutations
 LRU approximation is used in practice

 For large m > 4,


Random replacement can be as effective as LRU

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 37
Next . . .

 Random Access Memory and its Structure

 Memory Hierarchy and the need for Cache Memory

 The Basics of Caches

 Cache Performance and Memory Stall Cycles

 Improving Cache Performance

 Multilevel Caches

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 38
Hit Rate and Miss Rate
 Hit Rate = Hits / (Hits + Misses)
 Miss Rate = Misses / (Hits + Misses)
 I-Cache Miss Rate = Miss rate in the Instruction Cache
 D-Cache Miss Rate = Miss rate in the Data Cache
 Example:
 Out of 1000 instructions fetched, 150 missed in the I-Cache
 25% are load-store instructions, 50 missed in the D-Cache
 What are the I-cache and D-cache miss rates?

 I-Cache Miss Rate = 150 / 1000 = 15%


 D-Cache Miss Rate = 50 / (25% × 1000) = 50 / 250 = 20%
Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 39
Memory Stall Cycles
 The processor stalls on a Cache miss
 When fetching instructions from the Instruction Cache (I-cache)
 When loading or storing data into the Data Cache (D-cache)

Memory stall cycles = Combined Misses  Miss Penalty


 Miss Penalty: clock cycles to process a cache miss
Combined Misses = I-Cache Misses + D-Cache Misses
I-Cache Misses = I-Count × I-Cache Miss Rate
D-Cache Misses = LS-Count × D-Cache Miss Rate
LS-Count (Load & Store) = I-Count × LS Frequency
 Cache misses are often reported per thousand instructions

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 40
Memory Stall Cycles Per Instruction
 Memory Stall Cycles Per Instruction =
Combined Misses Per Instruction × Miss Penalty
 Miss Penalty is assumed equal for I-cache & D-cache
 Miss Penalty is assumed equal for Load and Store
 Combined Misses Per Instruction =
I-Cache Miss Rate + LS Frequency × D-Cache Miss Rate
 Therefore, Memory Stall Cycles Per Instruction =

I-Cache Miss Rate × Miss Penalty +


LS Frequency × D-Cache Miss Rate × Miss Penalty

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 41
Example on Memory Stall Cycles
 Consider a program with the given characteristics
 Instruction count (I-Count) = 106 instructions
 30% of instructions are loads and stores
 D-cache miss rate is 5% and I-cache miss rate is 1%
 Miss penalty is 100 clock cycles for instruction and data caches
 Compute combined misses per instruction and memory stall cycles

 Combined misses per instruction in I-Cache and D-Cache


 1% + 30%  5% = 0.025 combined misses per instruction
 Equal to 25 misses per 1000 instructions

 Memory stall cycles


 0.025  100 (miss penalty) = 2.5 stall cycles per instruction
 Total memory stall cycles = 106  2.5 = 2,500,000

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 42
CPU Time with Memory Stall Cycles

CPU Time = I-Count × CPIMemoryStalls × Clock Cycle

CPIMemoryStalls = CPIPerfectCache + Mem Stalls per Instruction

 CPIPerfectCache = CPI for ideal cache (no cache misses)

 CPIMemoryStalls = CPI in the presence of memory stalls

 Memory stall cycles increase the CPI

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 43
Example on CPI with Memory Stalls
 A processor has CPI of 1.5 without any memory stalls
 Cache miss rate is 2% for instruction and 5% for data
 20% of instructions are loads and stores
 Cache miss penalty is 100 clock cycles for I-cache and D-cache

 What is the impact on the CPI?


 Answer: Instruction data

Mem Stalls per Instruction = 0.02×100 + 0.2×0.05×100 = 3


CPIMemoryStalls = 1.5 + 3 = 4.5 cycles per instruction
CPIMemoryStalls / CPIPerfectCache = 4.5 / 1.5 = 3
Processor is 3 times slower due to memory stall cycles

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 44
Average Memory Access Time
 Average Memory Access Time (AMAT)
AMAT = Hit time + Miss rate × Miss penalty
 Time to access a cache for both hits and misses
 Example: Find the AMAT for a cache with
 Cache access time (Hit time) of 1 cycle = 2 ns
 Miss penalty of 20 clock cycles
 Miss rate of 0.05 per access

 Solution:
AMAT = 1 + 0.05 × 20 = 2 cycles = 4 ns
Without the cache, AMAT will be equal to Miss penalty = 20 cycles

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 45
Next . . .

 Random Access Memory and its Structure

 Memory Hierarchy and the need for Cache Memory

 The Basics of Caches

 Cache Performance and Memory Stall Cycles

 Improving Cache Performance

 Multilevel Caches

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 46
Improving Cache Performance
 Average Memory Access Time (AMAT)

AMAT = Hit time + Miss rate * Miss penalty

 Used as a framework for optimizations


 Reduce the Hit time
 Small and simple caches

 Reduce the Miss Rate


 Larger cache size, higher associativity, and larger block size

 Reduce the Miss Penalty


 Multilevel caches

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 47
Small and Simple Caches
 Hit time is critical: affects the processor clock cycle
 Fast clock rate demands small and simple L1 cache designs

 Small cache reduces the indexing time and hit time


 Indexing a cache represents a time consuming portion
 Tag comparison also adds to this hit time

 Direct-mapped overlaps tag check with data transfer


 Associative cache uses additional mux and increases hit time

 Size of L1 caches has not increased much


 L1 caches are the same size on Alpha 21264 and 21364
 Same also on UltraSparc II and III, AMD K6 and Athlon
 Reduced from 16 KB in Pentium III to 8 KB in Pentium 4!

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 48
Classifying Misses – Three Cs
 Conditions under which misses occur
 Compulsory: program starts with no block in cache
 Also called cold start misses
 Misses that would occur even if a cache has infinite size

 Capacity: misses happen because cache size is finite


 Blocks are replaced and then later retrieved
 Misses that would occur in a fully associative cache of a finite size

 Conflict: misses happen because of limited associativity


 Limited number of blocks per set
 Non-optimal replacement algorithm

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 49
Classifying Misses – cont’d

Compulsory misses are independent of cache size


Very small for long-running programs
Miss Rate
14% Capacity misses decrease as capacity
1-way
increases
12%
2-way
10% Conflict misses decrease as
4-way associativity increases
8%
8-way Data were collected using
6%
Capacity LRU replacement
4% Compulsory
2%
0
1 2 4 8 16 32 64 128 KB

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 50
Larger Size and Higher Associativity

 Increasing cache size reduces capacity misses

 It also reduces conflict misses

 Larger cache size spreads out references to more blocks

 Drawbacks: longer hit time and higher cost

 Larger caches are especially popular as 2nd level caches

 Higher associativity also improves miss rates

 Eight-way set associative is as effective as a fully associative

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 51
Larger Block Size
 Simplest way to reduce miss rate is to increase block size
 However, it increases conflict misses if cache is small

25% Increased Conflict Misses


Reduced
20% Compulsory
Misses
1K
64-byte blocks
Miss Rate

15% 4K are common in


L1 caches
10% 16K
128-byte block
64K are common in
5% L2 caches
256K
0%
32

64
16

256
128

Block Size (bytes)

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 52
Multilevel Caches
 Top level cache should be kept small to
 Keep pace with processor speed

 Adding another cache level I-Cache D-Cache

 Can reduce the memory gap


Unified L2 Cache
 Can reduce memory bus loading
Main Memory
 Local miss rate
 Number of misses in a cache / Memory accesses to this cache
 Miss RateL1 for L1 cache, and Miss RateL2 for L2 cache

 Global miss rate


Number of misses in a cache / Memory accesses generated by CPU

Miss RateL1 for L1 cache, and Miss RateL1  Miss RateL2 for L2 cache

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 53
Power 7 On-Chip Caches [IBM 2010]

32KB I-Cache/core
32KB D-Cache/core
3-cycle latency

256KB Unified
L2 Cache/core
8-cycle latency

32MB Unified
Shared L3 Cache
Embedded DRAM
25-cycle latency
to local slice

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 54
Multilevel Cache Policies
 Multilevel Inclusion
 L1 cache data is always present in L2 cache

 A miss in L1, but a hit in L2 copies block from L2 to L1

 A miss in L1 and L2 brings a block into L1 and L2

 A write in L1 causes data to be written in L1 and L2

 Typically, write-through policy is used from L1 to L2

 Typically, write-back policy is used from L2 to main memory

 To reduce traffic on the memory bus

 A replacement or invalidation in L2 must be propagated to L1

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 55
Multilevel Cache Policies – cont’d
 Multilevel exclusion
 L1 data is never found in L2 cache – Prevents wasting space

 Cache miss in L1, but a hit in L2 results in a swap of blocks

 Cache miss in both L1 and L2 brings the block into L1 only

 Block replaced in L1 is moved into L2

 Example: AMD Athlon

 Same or different block size in L1 and L2 caches


 Choosing a larger block size in L2 can improve performance

 However different block sizes complicates implementation

 Pentium 4 has 64-byte blocks in L1 and 128-byte blocks in L2

Memory Hierarchy & Caches ICS 233 / COE 301 – Computer Organization © Muhamed Mudawar – slide 56

You might also like