On Thu, 3 Jan 2013, zhengchl wrote:
Hi,
When I used ruby cache coherence protocol MOESI_CMP_directory, I found that
when a replacement taking place, the protocol allocated a TBE entryand made
use of TBE entry instead of cache entry to complete a Replacement transition.
So, it looks like a replacement completes at once and the protocol can reuse
the cache entry without waiting for some cycles.
L1 Replacement:
i_allocateTBE;
d_issuePUTX;
kk_deallocateL1CacheBlock; // this cache block can be reused
without waiting for replacement completing.
Writeback Ack Data:
qq_sendWBDataFromTBE;
s_deallocateTBE;
l_popForwardQueue;
I'm strange is this possible in real world?
Having TBEs seems one of the possible ways to implement a coherence
protocol. I don't think they are necessary, but they don't seem
implausible.
--
Nilay
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
