lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 5 Jun 2007 14:57:21 -0400
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	Tom Moore <tmoore@...tial.ca>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 4Gb ram not showing up

On Mon, Jun 04, 2007 at 03:43:08PM -0400, Tom Moore wrote:
> Thank you for the reply back.  Your answer makes perfect sense to me, 
> and it is what I had suspected but was not sure about.  The math seems 
> to indicate that 4Gb of ram plus 1Gb of PCI address space equals 5Gb of 
> memory space.  So it does sound like I should have a larger kernel model.
> 
> What confused me the most (and still does), is the help message string 
> that is presented for the CONFIG_HIGHMEM4G option:
>  "Select this if you have a 32-bit processor and between 1 and 4 
> gigabytes of physical RAM."

A better description would be:

"Select this if you have a 32-bit processor and memory mapped in the 1GB
to 4GB address range."

> Well that sounds like the amount of memory that I have, so that is what 
> I selected.
> 
> Also, although I know what PAE stands for, I don't know how to select it 
> when building a kernel.  Would I get this from the CONFIG_HIGHMEM64G 
> option?  The help text for that says:
>  "Select this if you have a 32-bit processor and more than 4 gigabytes 
> of physical RAM."

That one would be better as:

"Select this if you have a 32-bit processor and ram mapped in the address
range above 4GB."

> This does not sound like it applies to my hardware.  There is something 
> wrong with my understanding, or with these message strings.  I am still 
> confused.

In the past a number of machines couldn't remap memory, so you simply
lost any that was covered by the PCI address space.  In that case 4GB
ram mean you got 3GB or 3.5GB ram, and turning on HIGHMEM64G wouldn't
help.

In your case with some ram mapped above 4GB, you want the option that
supports up to 64GB ram (the limit of PAE) which is the
CONFIG_HIGHMEM64G.  After all since some ram is mapped between 4 and
5GB, it is as if you had 5GB ram, but the part between 3 and 4GB was
covered up.  You are just lucky enough that the covered up part got
moved out of the way instead so you get to use it.

--
Len Sorensen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ