Date: | Wed, 3 Dec 2008 17:55:16 -0500 |
---|---|
From: | "Ashwath Narasimhan" <nashwath@xxxxxxxxx> |
Subject: | Re: [Gems-users] Direct Mapped cache query |
Yes I was getting the assertion in PseudoLRUPolicy. Ok I will modify the code to support direct replacement. Thanks for the Tip. regards, Ashwath On Wed, Dec 3, 2008 at 5:46 PM, Polina Dudnik <pdudnik@xxxxxxxxx> wrote: I suspect the assertion you are getting is in PseudoLRUPolicy::PseudoLRUPolicy(Index, Index)? The problem is that the replacement policy implemented requires set-associativity. So, what you can do is modify the code in PseudoLRUPolicy.h to say if associativity is one, then just replace. Does that make sense? |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | Re: [Gems-users] Direct Mapped cache query, Derek Hower |
---|---|
Next by Date: | Re: [Gems-users] Direct Mapped cache query, Polina Dudnik |
Previous by Thread: | Re: [Gems-users] Direct Mapped cache query, Derek Hower |
Next by Thread: | Re: [Gems-users] Direct Mapped cache query, Polina Dudnik |
Indexes: | [Date] [Thread] |