From owner-freebsd-arch@FreeBSD.ORG Thu Sep 9 09:09:38 2010 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D44C10656EF for ; Thu, 9 Sep 2010 09:09:38 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 0469B8FC1B for ; Thu, 9 Sep 2010 09:09:37 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id o898QwQq047788 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Sep 2010 11:26:58 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id o898QvB6005481; Thu, 9 Sep 2010 11:26:57 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id o898Qv7L005480; Thu, 9 Sep 2010 11:26:57 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 9 Sep 2010 11:26:57 +0300 From: Kostik Belousov To: Andriy Gapon Message-ID: <20100909082657.GJ2465@deviant.kiev.zoral.com.ua> References: <4C4DB2B8.9080404@freebsd.org> <4C4DD1AA.3050906@freebsd.org> <4C8894E4.2030804@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LQAwcd5tHl0Qlnzi" Content-Disposition: inline In-Reply-To: <4C8894E4.2030804@freebsd.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-2.2 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_50, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-arch@freebsd.org Subject: Re: amd64: change VM_KMEM_SIZE_SCALE to 1? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Sep 2010 09:09:38 -0000 --LQAwcd5tHl0Qlnzi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 09, 2010 at 11:03:48AM +0300, Andriy Gapon wrote: > on 26/07/2010 22:29 Peter Wemm said the following: > >=20 > > That hard limit of 512G of physical ram doesn't seem so distant anymore= .. >=20 > I was reviewing this thread and got curious about this statement. > What is this limit? Where does it come from? I do not think that such limit is enforced by hardware. In the recent Intel x86 sw architecture specification, there is a statement (vol 3a, 4.1.4): CPUID.80000008H:EAX[7:0] reports the physical-address width supported by the processor. (For processors that do not support CPUID function 80000008H, the width is generally 36 if CPUID.01H:EDX.PAE [bit 6] =3D 1 and 32 otherwi= se.) This width is referred to as MAXPHYADDR. MAXPHYADDR is at most 52. I suspect that "512GB" might refer to the current direct map sizing in the amd64 pmap module. The direct map is provided by single entry in pml4 table, that allows to map 512GB. --LQAwcd5tHl0Qlnzi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkyImlEACgkQC3+MBN1Mb4hn7ACeLy82tA2YE49RoolzC/hfiqrD kfAAn2cK7Dz0xWpl+YIczEQTrqnH/tEO =l3CR -----END PGP SIGNATURE----- --LQAwcd5tHl0Qlnzi--