DESIGN ASSIGNMENT - 1 GROUP 6

190350 - Gurugubelli Navya

190657 - SriLekha

PART 1 :Simulation of L2 and L3 Caches

POLICY CACHE bzip2 gcc gromace h264ref hmmer sphinx3

INCLUSIVE L2 HITS 5259461 115743 300046 1378895 1766344 1933098

50

INCLUSIVE L2 MISSES 5398166 303646 336851 969678 1743421 8820349

1

INCLUSIVE L3 HITS 3951778 166305 166320 627532 1352195 612987

9

INCLUSIVE L3 MISSES 1446388 137340 170531 342146 391226 8207362

2

NINE L2 HITS 5260051 115810 3094787 1382949 1774443 1938317

02

NINE L2 MISSES 5397576 302980 336724 965624 1735322 8815130

9

NINE L3 HITS 3951730 166356 166265 632041 1358978 609986

1

NINE L3 MISSES 1445846 136624 170459 333583 376344 8205144

8

EXCLUSIVE L2 HITS 5260051 115810 3094787 1382949 1774443 1938317

02

EXCLUSIVE L2 MISSES 5397576 302980 336724 965624 1735322 8815130

9

EXCLUSIVE L3 HITS 4508355 178698 177422 821943 1435276 1594354

5

EXCLUSIVE L3 MISSES 889221 124282 159302 143681 300046 7220776

4
Observations :

1. L2 Misses & Hits are same in both exclusive and nine policies
This is seen because at any point of time the addresses present in L2 cache are the
same while executing using EXCLUSIVE and NINE policies but not in case of
INCLUSIVE.

This is because when we evict a block from L3 cache we need to invalidate it in L2

cache in the case of inclusive policy, whereas this is not done in other 2 policies.

This can be seen as follows:

In exclusive policy, when an L3 hit takes place, it is invalidated in L3 and gets added
to L2 cache.
In NINE policy, when an L3 hit takes place, it gets added to the L2 cache.
In exclusive policy, when an L3 miss takes place, it is added to the L2 Cache.
Whereas in NINE policy, it gets added to both L2 and L3 cache.
Since both the policies change the L2 cache in the same manner during L2 hits and
L3 misses, there is no difference in the number of hits and misses observed in the
L2 cache.

2. There is very less miss rate in L3 in exclusive policy when compared to other 2
policies.
In exclusive policy, at any point of time, we don’t have the same block present in
both L2 and L3 cache which saves a lot of space in L3 cache decreasing the miss
rate.

3. There isn’t much difference between L3 miss rates in

inclusive and nine policies
Inclusive policy has a slightly larger miss rate than nine policy because in inclusive
policy as soon as a block is evicted in L3 we evict it from L2 also, which increases
the miss rate.

4. L2 misses in Inclusive policy is large

This happens because when we evict a block from L3 cache in inclusive policy we
need to evict it from L2 as well irrespective of if it LRU block or not, which increases
its miss rates as compared to others.
Part 2

Fully Associative L3 Cache using LRU replacement policy

INCLUSIVE Cold Capacity Conflict

bzip2 119753 1241577 85058

gcc 773053 596546 3803

gromacs 107962 61367 1202

h264ref 63703 271120 7323

hmmer 75884 297539 17803

sphinx3 122069 8265188 -179895

Inorder to generate the cold misses(compulsory), the count of unique address accesses is
calculated. To calculate the number of Capacity misses, the conflict misses is made 0 by
making L3 cache Fully Associative. Thus the number of Capacity becomes Total Number of
misses in FA L3 cache - Number of cold misses.

The conflict misses, is 16-way L3 misses - FA L3 misses