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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110726194956.GA4117@tassilo.jf.intel.com>
Date:	Tue, 26 Jul 2011 12:49:56 -0700
From:	Andi Kleen <ak@...ux.intel.com>
To:	Bob Zhang <zhanglinbao@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	hayfeng Lee <omycle@...il.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Bob Zhang <2004.zhang@...il.com>
Subject: Re: x86_64 virtual memory map

> and in the end of mm.txt , it says :
> >>Current X86-64 implementations only support 40 bits of address space,
>  >> 27but we support up to 46 bits. This expands into MBZ space in the
> >>page tables.
> so this 40bit(1TB) is responding to virtual memory map(1TB) ?

The 1TB limit was dropped a long time ago.
Your googling found an old file.

> 3,  if I installed 64TB physical memory (RAM) , but linux kernel only

What system is that out of curiosity? Are you sure it's not
a cluster?

> support 1TB address space , what should I do next ?

There's no known 1TB limit currently.

However at least for Intel Xeons there is no CPU which supports
more than 16TB physical address space.

Are you sure you have your units correct?

The theoretical x86 kernel limits are higher and it should upto support
64TB. However since that's untested territory and there 
have been bugs in large memory support in the past
you may run into problems.

Other architectures like IA64 will support more (but you
may be also in untested territory)

I believe 4+TB x86 systems have been tested.

-Andi

--
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