Date: | Wed, 3 Dec 2008 17:33:21 -0500 |
---|---|
From: | "Ashwath Narasimhan" <nashwath@xxxxxxxxx> |
Subject: | Re: [Gems-users] Direct Mapped cache query |
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? On Wed, Dec 3, 2008 at 5:10 PM, Polina Dudnik <pdudnik@xxxxxxxxx> wrote: There are two assertions in RubyConfig.C, which performs bounds checking on parameters. Is an assertion failure the error you are getting? If so, you need to make sure that your parameters satisfy the assertion. |
[← 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, Polina Dudnik |
Previous by Thread: | Re: [Gems-users] Direct Mapped cache query, Polina Dudnik |
Next by Thread: | Re: [Gems-users] Direct Mapped cache query, Polina Dudnik |
Indexes: | [Date] [Thread] |