block-inclusivecache-sifive
block-inclusivecache-sifive copied to clipboard
If way0 has been used, new miss req may pick way0 to use even other ways were empty?
There is no lock way design? if no hit, no tagmatch, no bypass, it just picked victimway which is "random" generated by LFSR.
Hi xiaochunsong92,
I met the similar issue, when I send the continuous read req with the same set at A channel, it seems it always access the first way of the set, instead of different ways within the same set, even the request address has the same set and different tags.
Have you already solved the problem?
best, Jimmy