Hi Muhammad,
Generally, if sendTimingReq fails, you have to save the packet so you can
resend it. In my Learning gem5 code, I *try* to simplify the retry logic so
that this is hidden. Instead of saving the packet in the cache code, the
packet is saved in the port code. Also, the code in Learning
Dear Jason,
Thkns for the response. Just another quick question.
What if memory was busy when u call the "sendTiimingReq" for WritebackDirty
packet. In insert() function, when you call memport.sendTimingReq for
WritebackDirty blocks, you don't save them in blocked Packet, in case
Memory is
Hello,
No. You should not have a response for WritebackDirty. In fact, most (all?)
writes do not have responses. See src/mem/packet.cc. (
https://gem5.googlesource.com/public/gem5/+/master/src/mem/packet.cc#80)
Some commands have the "NeedsResponse" flag set. If so, this request will
be turned
Hello All,
Following jason's website, created my own cache.
On Cache miss, I send the TimingReq to memory, and get the response, which
I handle in "handleResponse".
during HandleResponse, in case the insertion causes eviction (cache was
full), the insert function generates another
