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 for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 30 Apr 2008 17:02:02 +0200
From:	Fabio De Francesco <fabiomdf@...ce.it>
To:	linux-kernel@...r.kernel.org
Subject: [x86_32] With 4GB installed, in which cases low mem total is less than 896MB?

Hi all,

I've got a Linux box, Intel Core 2 T7700 with 4GB RAM installed, with vanilla kernel 2.6.24 + TuxOnIce patch-set compiled for x86_32bit (CONFIG_X86_32=y), whose /proc/meminfo shows "LowTotal 794MB".

I've always known that, in this specific platform, Linux permanently maps 896MB as "Low Memory" into its linear address space (as this last value is the one /proc/meminfo shows in the other two x86_32bit computers I own). 

What am I missing?

A further issue is about the "MemTotal" value that only shows more or less 3550MB with HIGHMEM4G selected, and it shows a  more satisfying value of 4050MB with HIGHMEM64G + X86_PAE + RESOURCES_64BIT selected. In both cases LowTotal is always less than 800MB.

Why is it needed to activate the PAE mechanism in order to see and use the whole 4GB memory? Is it what it is expected to be done?

Thanks in advance to anyone who will reply.

Regards,

fabio de francesco
metanix.org
--
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