linux-kernel - Re: x86_64 virtual memory map

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-prev] [day] [month] [year] [list]

Message-ID: <CAKdQVUbmMca+iV6yzrBy0Rcuw6YQn3pMin3+_iQC4=vg_bMtPA@mail.gmail.com>
Date:	Fri, 19 Aug 2011 23:13:46 +0800
From:	Bob Zhang <zhanglinbao@...il.com>
To:	Andi Kleen <ak@...ux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: x86_64 virtual memory map

in fact , there are two factors to affect how much DRAM final user can use .

for example , for HP's this kind of machine , BIOS can support 40-bit
size and 44 -bit size.
if in BIOS ,user select 44-bit size , then every CPU(socket) can
support 512GB , if user install 8 CPU(socket) , it totally support
4TB.
if in BIOS ,user select 40-bit size , then every CPU(socket) only can
support 128GB , so if user install 8s(socket) , it totally only can
support 1TB, if 4s, only support totally 512GB.

certainly ,this is also decided by OS support 44-bit size or not. if
OS,i.e. rhel5.x  , only support 40bit ,though BIOS 44-bit selected ,
only 40-bit size support every CPU(socket).
--
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/