{ "numMessagesInTopic": 7, "nextInTime": 1949, "senderId": "hhwYHt6W5mscx8AUKbH5okKSvzAeL0FTk0i7vnL6_YXAg4PHYzn7tCau4NwLdZh3-pE07Q74S4nQ2uQipNOINY8p-5BTKWEPf6c", "systemMessage": false, "subject": "Re: Anyone know if a 1GB ram stick work in a SG 20?", "from": "slargbot <no_reply@yahoogroups.com>", "authorName": "slargbot", "msgSnippet": "another thing worth mentioning is that the reason himem is not enabled by default is that is has a small but not insignificant performance hit -- in fact, I", "msgId": 1948, "profile": "slargbot", "topicId": 1927, "spamInfo": { "reason": "0", "isSpam": false }, "replyTo": "LIST", "userId": 168935299, "messageBody": "
--- In magnia_sg20@yahoogroups.com, Brian Wilson <bwilson@c...> wrote:
\n> On Fri, 26 Mar 2004, Nigel Marston wrote:
\n> > I installed 2 x 512Mb on a stock 2.5 (yep two point FIVE) image.
\nbut it only
\n> > displayed 900-odd Mb.
\n>
\n> To support > 960MB the kernel has to be recompiled with 'himem'
\n> support. Stock Linux distros generally still come with this feature
\n> turned off since we have only recently gotten to the point where > 1GB
\n> has become affordable. Here is an excerpt from the kernel
\n> documentation.
\n>
\n> # Choice: himem
\n> High Memory support
\n> CONFIG_NOHIGHMEM
\n> Linux can use up to 64 Gigabytes of physical memory on x86 systems.
\n> However, the address space of 32-bit x86 processors is only 4
\n> Gigabytes large. That means that, if you have a large amount of
\n> physical memory, not all of it can be "permanently mapped" by the
\n> kernel. The physical memory that's not permanently mapped is called
\n> "high memory".
\n>
\n> If you are compiling a kernel which will never run on a machine with
\n> more than 960 megabytes of total physical RAM, answer "off" here
\n(default
\n> choice and suitable for most users). This will result in a "3GB/1GB"
\n> split: 3GB are mapped so that each process sees a 3GB virtual memory
\n> space and the remaining part of the 4GB virtual memory space is used
\n> by the kernel to permanently map as much physical memory as
\n> possible.
\n>
\n> ...more stuff deleted...
\n>
\n>
\n> Brian