[gem5-users] Re: Lock implementation in Ruby Cache Memory and Request Queue

Hi Gabriel, Thanks a lot for your reply. Best wishes, Congwu Zhang > On Sep 1, 2023, at 13:46, gabriel.busnot--- via gem5-users > wrote: > > Hi, > > For 1, I meant automatically: “lines will not get blocked automatically”. > > As for 2, peek does not block anything unless you use the bloc

[gem5-users] Re: Lock implementation in Ruby Cache Memory and Request Queue

Hi, For 1, I meant automatically: “lines will not get blocked automatically”. As for 2, peek does not block anything unless you use the block_on mechanism. You can peek as many queues as you want as well as dequeue and enqueue as many as you want. Regards, Gabriel

[gem5-users] Re: Lock implementation in Ruby Cache Memory and Request Queue

again for your reply! Best Wishes, Congwu Zhang -Original Messages- From:"gabriel.busnot--- via gem5-users" Sent Time:2023-08-30 22:20:17 (Wednesday) To: gem5-users@gem5.org Cc: gabriel.bus...@arteris.com Subject: [gem5-users] Re: Lock implementation in Ruby Cache Memory and

[gem5-users] Re: Lock implementation in Ruby Cache Memory and Request Queue

Hi, 1. First, isLocked is part of the implementation of atomics based on load-linked-store-conditional. When processing a request in ruby controllers, lines will not get blocked manually. In order to avoid request hasards, several mechanisms are available. 1. The block_on mechanism of peek.