Right now it's possible the redefine the mandatoryQueueLatency function to
return the cache latency, but this only works for L1 hit latency. It's
currently not possible to have a fully generic model since each protocol can
have different assumptions regarding how a cache lookup/update latency wo
Thank you very much for your reply and explanation, Tiago!
Wouldn't it be more generic to add the latencies at the time of performing
the access in the cache itself instead of having it in the controllers
since any cache access should incur access latency? I am not sure how easy
that would be thou
