You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When bsg_cache has a miss. it fills the new data and then goes to a "recover" state, where it re-reads tag and data mems in TL. I believe this step can be omitted if v_tl_r == 0, since the memory data in that stage will be unused anyway. This has three major benefits:
Saves power by not rereading the RAMs
Saves a cycle of latency on miss
Saves a cycle of latency on hit-after miss
The text was updated successfully, but these errors were encountered:
I agree when using bsg_cache as an L2 with cacheline-oriented operations, but this is very common for an L1 with a random access pattern. I discovered this when analyzing the performance of a different cache and using bsg_cache as a reference
taylor-bsg
changed the title
bsg_cache optimization opportunity
bsg_cache -- don't replay TL instruction if there is no TL instruction
Oct 12, 2022
taylor-bsg
changed the title
bsg_cache -- don't replay TL instruction if there is no TL instruction
bsg_cache optimization -- don't replay TL instruction if there is no TL instruction
Oct 12, 2022
When bsg_cache has a miss. it fills the new data and then goes to a "recover" state, where it re-reads tag and data mems in TL. I believe this step can be omitted if v_tl_r == 0, since the memory data in that stage will be unused anyway. This has three major benefits:
The text was updated successfully, but these errors were encountered: