Xen devel - Nov 2005 - 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?
If we wanted to access 64 GB what else would need to be fixed?
Thanks
Raj

PS. I tried changing MACPHYS_MBYTES to 64 and it didn''t seem to break
anything. Of course, I am running on a 4 GB system.

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

> 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@lists.xensource.com
http://lists.xensource.com/xen-devel