WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork for 64-bit

To: Andi Kleen <andi@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork for 64-bit Xen support
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 25 Jun 2008 20:22:58 +0100
Cc: Mark McLoughlin <markmc@xxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Eduardo Habkost <ehabkost@xxxxxxxxxx>, Stephen Tweedie <sct@xxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>
Delivery-date: Wed, 25 Jun 2008 12:23:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080625191315.GD6708@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcjW+OAYHmuW1kLsEd2ISwAX8io7RQ==
Thread-topic: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork for 64-bit Xen support
User-agent: Microsoft-Entourage/11.4.0.080122
On 25/6/08 20:13, "Andi Kleen" <andi@xxxxxxxxxxxxxx> wrote:

>> What does Linux expect to scale up to? Reserving 16 PML4 entries leaves the
>> kernel with 120TB of available 'negative' address space. Should be plenty, I
>> would think.
> 
> There are already (ok non x86-64) systems shipping today with 10+TB of
> addressable memory. 100+TB is not that far away with typical
> growth rates. Besides there has to be much more in the negative address
> space than just direct mapping.

There are obviously no x64 boxes around at the moment with >1TB of regular
shared memory, since no CPUs have more than 40 address lines. 100+TB RAM is
surely years away.

If this is a blocker issue, we could just keep PAGE_OFFSET as it is when Xen
support is not configured into the kernel. Then those who are concerned
about 5% extra headroom at 100TB RAM sizes can configure their kernel
appropriately.

> So far we always that 64bit Linux can support upto 1/4*max VA memory.
> With your change that formula would be not true anymore.

Does the formula have any practical significance?

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork for 64-bit Xen support, Keir Fraser <=