Hello, John,
I have sent you the link to the last patch in the series. On the right there is 
a list (called Relation Chain) containing the links to the 4 patches. I will 
copy and paste the links here, just in case:
1st: https://gem5-review.googlesource.com/c/public/gem5/+/37895/12nd: 
https://gem5-review.googlesource.com/c/public/gem5/+/37896/13rd: 
https://gem5-review.googlesource.com/c/public/gem5/+/37897/14th: 
https://gem5-review.googlesource.com/c/public/gem5/+/37898/1
To download them, you go to the top right corner, to the three vertical dots. 
Click on "Download Patch" (NOT Cherry Pick) and then a new window will pop up, 
which allows you to select how you will download. If downloading individually, 
copy the cherry pick command and run locally. If you want to download the whole 
patch chain at once go to the 4th patch in the series and select "Checkout".
Ideally you'd want to cherry-pick, because then you'd keep using the stable 
gem5 version; however when cherry picking you will need to cherry-pick other 
patches for this to work (I think picking 
https://gem5-review.googlesource.com/c/public/gem5/+/37135 would be enough).
Regarding SRRIP, it is implemented as RRIPRP().
Regards,Daniel
    Em sábado, 21 de novembro de 2020 22:40:48 GMT+1, John H 
<[email protected]> escreveu:  
 
 Hi
Thanks for the reply. I don't know how to access the entire code about which 
you mentioned in the email. I can only see a 2 line change in 
ReplacementPolicies.py in the patch. Can you please provide me with the entire 
patch file(all the changes required for DRRIP for your implementation) if 
that's ok with you.That will really help me to understand it.
Also is SRRIP implemented in the new gem5?
Thanks
John
On Sat, Nov 21, 2020 at 10:27 AM Daniel Carvalho <[email protected]> wrote:

 Hello, John,

I have uploaded for review some patches to make DRRIP work: 
https://gem5-review.googlesource.com/c/public/gem5/+/37898I believe the code is 
well documented enough to help you understand how it works.

To use DRRIPRP you must set the constituency size and the number of entries per 
team per constituency (team size) on instantiation.
As an example, if:- table size=32KB- associativity=4
And we want:- 32 dedicated sets per team
Then we'd instantiate DRRIPRP(constituency_size=1024, team_size=4)
Since, IIRC, there is no analysis in the paper describing why specifically pick 
complements, instead of implementing DIP's complement-select policy, I 
implemented a "consecutive-select" policy (i.e., pick the first team_size 
entries of the set to be samples for team 0, and the next team_size entries of 
the set to be samples for team 1). If you really want that policy, you can 
implement it easily by modifying DuelingMonitor::initEntry.

Regards,Daniel
   Em sábado, 21 de novembro de 2020 03:46:27 GMT+1, John H via gem5-users 
<[email protected]> escreveu:  
 
 Hello,
I am new with gem5, just getting started. I wanted to implement DRRIP cache 
replacement policy. Have any one of you tried implementing this? Any pointers 
on this would be helpful.
Thanks,
John_______________________________________________
gem5-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s  
  
_______________________________________________
gem5-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Reply via email to