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: tmem - really default to on?

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] RE: tmem - really default to on?
From: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Date: Tue, 9 Feb 2010 13:59:14 +0000
Cc: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Christian Limpach <Christian.Limpach@xxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Tue, 09 Feb 2010 05:59:41 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C797141B.990E%keir.fraser@xxxxxxxxxxxxx>
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: <4B716A96020000780002E73E@xxxxxxxxxxxxxxxxxx> <C797141B.990E%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
At 13:31 +0000 on 09 Feb (1265722267), Keir Fraser wrote:
> On 09/02/2010 13:00, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:
> 
> >> I think the correct approach to all of this is to move system-wide to
> >> allocating memory in 2MB contiguous aligned chunks.  There's no sense in
> >> doing guest allocations any finer-grained than that and there are
> >> noticeable performance wins from all the superpage support that's gone
> >> in recently.  Then little things like needing 16k contiguous areas just
> >> go away.
> > 
> > I have to admit that I can't see how this would work with ballooning,
> > or (if the balloon driver was adjusted to deal with this) with
> > fragmentation inside Dom0 (or any other guest that memory is
> > intended to be removed from). Nor am I sure tmem could be
> > changed to deal with 2Mb chunks instead of 4k ones.
> 
> Balloon driver is the obvious fly in the ointment that I can see, too.

Good point.  That's going to be a problem for HVM ballooning, especially
on EPT/NPT where having superpage allocations makes a big difference.

In the meantime we can fix the shadow code.  Unfortunately I won't be
able to look at it immediately but maybe Christian has a patch.

Tim.

-- 
Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, XenServer Engineering
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

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