Re: [Xen-devel] Fw: bigphysarea patch on xen capable linux

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

You can increase MAX_CONTIG_ORDER and then it could work. The cost is a
larger kernel image size for the enlarged static arrays defined immediately
above xen_create_contiguous_region().

 -- Keir

On 12/01/2010 20:49, "Kashmira. K." <chimnee@xxxxxxxxx> wrote:

> 
> Hi Jan,
> 
> I looked at the linux code xen_create_contiguous_region(). It appears the 2MB
> limit comes from the #define MAX_CONIG_ORGER 9. Could that be modified to get
> more than 2MB. 
> 
> If not would you have other suggestions of how I can I get around 500M or more
> of physically contiguous memory on Xen in Dom0 linux.
> 
> Thanks
> Kashmira
> 
> --- On Tue, 1/12/10, Jan Beulich <JBeulich@xxxxxxxxxx> wrote:
> 
>> From: Jan Beulich <JBeulich@xxxxxxxxxx>
>> Subject: Re: [Xen-devel] Fw: bigphysarea patch on xen capable linux
>> To: "Kashmira. K." <chimnee@xxxxxxxxx>
>> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>> Date: Tuesday, January 12, 2010, 12:53 AM
>>>>> "Kashmira. K." <chimnee@xxxxxxxxx>
>> 08.01.10 02:10 >>>
>>> 1. Is the bigphysarea patch supported on Xen capable
>>> linux?  If not what is the maximum physically
>>> contiguous memory Xen provides.
>> 
>> 2Mb is the maximum you can create.
>>  
>>> 2. If I were to run my application in DomU instead of
>> Dom0,
>>> can the bigphysarea patch  be used then.
>> 
>> In a fully virtualized DomU this should be possible (unless
>> you imply to
>> be able to use 1G pages).
>> 
>> Jan
>> 
>> 
> 
> 
>       
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



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