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

[Xen-devel] Re: [PATCH 3/3] xen: use maximum reservation to limit dom0 m

To: David Vrabel <david.vrabel@xxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 3/3] xen: use maximum reservation to limit dom0 memory
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Tue, 16 Aug 2011 10:50:31 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 16 Aug 2011 07:51:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110816135352.GD30261@xxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1313488838-28809-1-git-send-email-david.vrabel@xxxxxxxxxx> <1313488838-28809-4-git-send-email-david.vrabel@xxxxxxxxxx> <20110816135352.GD30261@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
On Tue, Aug 16, 2011 at 09:53:52AM -0400, Konrad Rzeszutek Wilk wrote:
> On Tue, Aug 16, 2011 at 11:00:38AM +0100, David Vrabel wrote:
> > Use the maximum reservation hypercall to set limit the amount of
> > usable dom0 memory.  This reduces the size of pages tables etc. if
> > dom0 is to use less memory than the maximum available.
> 
> Ok, so it sounds like this patch by itself can fix the "more page tables
> than we need" issue.
> 
> If so, I would prefer that you stick the tiny piece of code that
> calls the xen_get_max_pages() from the setup in this patch. This way
> we can backport this particular patch to stable tree without including
> the other patchsets you have posted. And it is a nicely contained
> one-patch-fixes-the-problem.
> 
> > 
> > Signed-off-by: David Vrabel <david.vrabel@xxxxxxxxxx>
> > ---
> > Note this requires a patched Xen that sets max_pages when creating dom0.
> 
> Please mention in the description the c/s and the name of the patch.
> 
> > ---
> >  arch/x86/xen/setup.c |    7 ++++++-
> >  1 files changed, 6 insertions(+), 1 deletions(-)
> > 
> > diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
> > index 3421c9e..584e7dc 100644
> > --- a/arch/x86/xen/setup.c
> > +++ b/arch/x86/xen/setup.c
> > @@ -197,7 +197,12 @@ static unsigned long __init xen_get_max_pages(void)
> >     unsigned long max_pages = MAX_DOMAIN_PAGES; /* Limited by memory map. */
> >  
> >     if (xen_initial_domain()) {

This actually is not neccessary? You could remove this and it would work
fine under DomU cases too I think. The only issue would be when running
this under older hypervisors as dom0 and getting ~0 as the max_pages - but
the 'min' clamping should solve that?

> > -           /* FIXME: ask hypervisor for max pages. */
> > +           domid_t domid = DOMID_SELF;
> > +           int ret;
> > +
> > +           ret = HYPERVISOR_memory_op(XENMEM_maximum_reservation, &domid);
> > +           if (ret > 0)
> > +                   max_pages = ret;
> Don't you want to clamp it? Say MAX_DOMAIN_PAGES is set to 1GB, and you
> set it to 2GB here - that will blow the P2M out. Perhaps
>         max_pages = min(ret, max_pages); ?
> 
> >     }
> >  
> >     return min(max_pages, MAX_DOMAIN_PAGES);
> > -- 
> > 1.7.4.1

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