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
The DRAM data return is stored in a PISO and then drained. For some configurations if the core is slow and DRAM is fast, the data can back up in the PISO. If there are multiple outstanding reads, then the PISO can overflow.
Multiple outstanding requests can come from non-blocking caches or a prefetcher for a blocking cache.
The simplest fix is to have a DRAM response data fifo the size of a (parametrized) number of read requests, so that it degenerates to the current hardware for 1 outstanding read request
The text was updated successfully, but these errors were encountered:
* prevent unnecessary icache read after icache miss; get rid of mem_addr_sent, icache miss pc dff
* icache miss test
* fix
* fix
* icache miss flush test
* simplify
* clean
* clean
* icache two words block
* save
* save
* fix
* use sram no write mask
* fix energy benchmark
* update
* update path to vcache
* fix
* fix
* energy_loop_test
* energy_loop_test run parallel
* icache block size = 4
* synth fix
* add comments/link to diagram
* add icache_block_size_in_words_p at toplevel
The DRAM data return is stored in a PISO and then drained. For some configurations if the core is slow and DRAM is fast, the data can back up in the PISO. If there are multiple outstanding reads, then the PISO can overflow.
Multiple outstanding requests can come from non-blocking caches or a prefetcher for a blocking cache.
The simplest fix is to have a DRAM response data fifo the size of a (parametrized) number of read requests, so that it degenerates to the current hardware for 1 outstanding read request
The text was updated successfully, but these errors were encountered: