Page 1 of 1

cache replacement policy

Posted: Sun May 30, 2021 11:06 am
by BeaRi
If L2-Cache (SSD) is full, PrimoCache seems to replace the first stored blocks with new ones, likely FIFO.

Was it able to add something like a timestamp, refreshed every time a block loads from L2 (mark them as new), so that the 'oldest' used blocks will be replaced?

(sorry for my english)

Re: cache replacement policy

Posted: Sun May 30, 2021 2:17 pm
by Jaga
The way I understand the cache to work, is on a Most Used vs Least Used algorithm. i.e. the Least Used blocks in the cache (those that are accessed the least often) are the first to go, while those with the Most Used number of accesses tend to stay in the cache.