Date: | Mon, 21 Apr 2008 10:01:38 -0500 |
---|---|
From: | "Mike Marty" <mike.marty@xxxxxxxxx> |
Subject: | Re: [Gems-users] question about LX_CACHE_NUM_SETS_BITS parameter |
RubyConfig.C will take the specified L2 parameters and divide it by the number of banks per chip. So right now, the L2 size is specified for the entire chip (spanning several shared banks). If you prefer specifying the L2 size per bank, comment out the single line of code in RubyConfig.C. In retrospect, doing it this way was probably a bad decision and leads to confusion. --mike On Sun, Apr 20, 2008 at 9:22 PM, Konstantinos Aisopos <kaisopos@xxxxxxxxx> wrote: thanks Mike. does the same happen with L2? If yes, isn't the default |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | Re: [Gems-users] Error loading Opal, Sasa Vitorovic |
---|---|
Next by Date: | [Gems-users] transactional memory and Opal, cge |
Previous by Thread: | Re: [Gems-users] question about LX_CACHE_NUM_SETS_BITS parameter, Konstantinos Aisopos |
Next by Thread: | Re: [Gems-users] question about LX_CACHE_NUM_SETS_BITS parameter, Konstantinos Aisopos |
Indexes: | [Date] [Thread] |