Date: | Wed, 3 Dec 2008 16:46:27 -0600 |
---|---|
From: | "Polina Dudnik" <pdudnik@xxxxxxxxx> |
Subject: | Re: [Gems-users] Direct Mapped cache query |
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? On Wed, Dec 3, 2008 at 4:33 PM, Ashwath Narasimhan <nashwath@xxxxxxxxx> wrote: That is correct Polina. i am getting an assertion failure. I cannot satisfy the assertion because I want to make it a direct mapped cache.Hence the associativity has to be 1. And If I do this, it gives rise to assertion failure. Ruby doesn't seem to allow associativity = 1. So how do configure Direct Mapped cache in Ruby? -- Polina Dudnik pdudnik@xxxxxxxxxxx http://pages.cs.wisc.edu/~pdudnik/ Department of Computer Sciences University of Wisconsin-Madison 6376 Computer Sciences & Statistics Bldg 1210 West Dayton Street Madison, WI 53706-1685 USA |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | Re: [Gems-users] Direct Mapped cache query, Polina Dudnik |
---|---|
Next by Date: | Re: [Gems-users] Direct Mapped cache query, Derek Hower |
Previous by Thread: | Re: [Gems-users] Direct Mapped cache query, Polina Dudnik |
Next by Thread: | Re: [Gems-users] Direct Mapped cache query, Derek Hower |
Indexes: | [Date] [Thread] |