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] 16 GB limit on Xen x86-32 PAE?

To: "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] 16 GB limit on Xen x86-32 PAE?
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 4 Nov 2005 21:29:55 -0000
Delivery-date: Fri, 04 Nov 2005 21:30:06 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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: AcXhfmC1OAYai4/4Q3quK9uGUtek4gAADw6QAACwJFA=
Thread-topic: [Xen-devel] 16 GB limit on Xen x86-32 PAE?
> I was trying to find out what the maximum limit for memory is 
> on x86-32 PAE. 
> I discovered that the limit was 16 GB and it was set in 
> xen/asm-x86/config.h
> 
> #define MACHPHYS_MBYTES        16 /* 1 MB needed per 1 GB memory */
> #define FRAMETABLE_MBYTES (MACHPHYS_MBYTES * 6)
> 
> Is there any reason for this 16 GB limit? Doesn't PAE permit 
> us to access up to 64 GB?

Xen currently uses 32 bytes of virtual address per machine page. Above
16GB, this is consuming significant amounts of virtual address space
that is normally available to the guest OS kernel, possibly causing
virtual memory balancing issues.  

> If we wanted to access 64 GB what else would need to be fixed?

It'll probably work, but you're on your own. Enabling CONFIG_HIGHPTE in
Linux will certainly help the balancing issue.

Longer term, if we want to go above 16GB we'll probably squeeze the
pfn_info structure to save some space, but this won't happen for 3.0.

Ian

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

<Prev in Thread] Current Thread [Next in Thread>