l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
September 2: Social gathering
Next Installfest:
TBD
Latest News:
Aug. 18: Discounts to "Velocity" in NY; come to tonight's "Photography" talk
Page last updated:
2009 Feb 03 23:31

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Kernel not seeing all my RAM
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Kernel not seeing all my RAM



Bill Broadley wrote:
> Cam Ellison wrote:
>   
>> Chanoch (Ken) Bloom wrote:
>>     
>>> I'm upgrading an x86 machine to 4 GB of RAM, and have compiled the
>>> kernel with CONFIG_HIGHMEM64G=y, but the kernel is only seeing 3283 MB
>>> of the RAM. Any idea what I'm doing wrong?
>>>
>>>   
>>>       
>> You should use the 4GB setting, I think.  The 64G setting is for a 
>> 64-bit processor, and you appear to have a 32-bit.
>>     
>
> Actually, I believe not.  The whole number of bits thing is rather confusing.
>  Is it the memory bus width?  Size of floating point?  Ints?
> Pointers/directly addressable ram?  Maximum addressable memory (ram)?
>
> Actually the "32-bit" intels (back at least to the P Pro) can address around
> 36 bits of memory via a hack, but only 4GB per process.  But the kernel could
> have 4GB and any single process could have 4GB, so on a large 32-bit server
> might have 16GB ram and allow for numerous processes to run as long as the
> total does go over 16, and any single process doesn't go over 1GB.  The config
> description should for CONFIG_HIHMEM64G should mention PAE or similar.
>
> Oh, as for the questions above:
> * it's not the memory width, 64-128 bits has been quite common for CPU
>   generations, currently it's often 192-256, and in a few weeks 384.
> * Floating point has been 64 bits for CPU generations
> * Ints aren't a bad approximation
> * Pointers aren't a bad approximation
> * addressable memory isn't
Well, as I go back and read what it actually says in xconfig, it's for a 
32-bit processor with more than 4G of RAM:

64GB (HIGHMEM64G)

Select this if you have a 32-bit processor and more than 4
gigabytes of physical RAM.

The 4GB setting is thus, and I think that's what he needs if he has a 
32-bit processor:

4GB (HIGHMEM4G)

Select this if you have a 32-bit processor and between 1 and 4
gigabytes of physical RAM.

As to my comments about 64-bit processors, I stand corrected.  And thank 
you, Bill, for the additional information.

I'm not going to quote what it says under "off" - it's too long - but 
maybe he should read that and see if he can't find the answer.  My 
interpretation is that it should be Off for a "64-bit processor".

HTH

Cam
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech



LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.