Re: [Gems-users] changing the replacement policy


Date: Wed, 22 Mar 2006 11:01:40 -0600 (CST)
From: Mike Marty <mikem@xxxxxxxxxxx>
Subject: Re: [Gems-users] changing the replacement policy
> I was trying to change the cache replacement policy for MSI_MOSI_CMP_directory
> to random and I ran into problems. It looks like the operation of the protocol
> is dependent on the replacement policy being LRU. Multiple calls to cacheProbe
> should return the same candidate for replacement.
> Is that true or I am missing something? Are there other coherence protocols
> which do not have this problem?
>

Ugh.  Definitely seems like a problem due to the lack of global variables
in SLICC.  It isn't dependent on LRU, only that subsequent calls (in the
same wakeup) to cacheProbe() return the same thing.  So any non-random
replacement policy would work.

I'll think about this and get back to you if I happen to come up with a
clean solution to using a random replacement policy.





[← Prev in Thread] Current Thread [Next in Thread→]