[gem5-users] Re: Read Miss Operation at Last Level Cache (LLC)

2023-12-08 Thread Eliot Moss via gem5-users
On 12/8/2023 1:31 AM, zahra moein via gem5-users wrote: Hello, Thank you very much for your response. I appreciate your assistance, and I made an effort to understand the code, which provided me with a better understanding. However, I couldn't determine the exact origin of the packet sent by

[gem5-users] Re: Read Miss Operation at Last Level Cache (LLC)

2023-12-07 Thread zahra moein via gem5-users
Hello, Thank you very much for your response. I appreciate your assistance, and I made an effort to understand the code, which provided me with a better understanding. However, I couldn't determine the exact origin of the packet sent by sendTimingResp() for it to be received by recvTimingResp(

[gem5-users] Re: Read Miss Operation at Last Level Cache (LLC)

2023-12-01 Thread Eliot Moss via gem5-users
On 12/1/2023 6:24 PM, zahra moein via gem5-users wrote: Thank you for your response. I would like to seek further clarification regarding the parameter RecvTimingResp: void BaseCache::recvTimingResp(PacketPtr pkt) Could you please confirm if this parameter represents a packet that is receive

[gem5-users] Re: Read Miss Operation at Last Level Cache (LLC)

2023-12-01 Thread zahra moein via gem5-users
Thank you for your response.\ \ I would like to seek further clarification regarding the parameter RecvTimingResp: \  void BaseCache::recvTimingResp(PacketPtr pkt)\ \ Could you please confirm if this parameter represents a packet that is received from memory? If it does, I would appreciate your

[gem5-users] Re: Read Miss Operation at Last Level Cache (LLC)

2023-11-30 Thread Eliot Moss via gem5-users
On 11/30/2023 2:07 PM, zahra moein via gem5-users wrote: Hi everyone, As we already know, a "Read miss" at the last cache level (LLC) means that the desired block in the LLC for reading was not found. Consequently, it is necessary to locate a victim block and copy the desired block from the mai