Xen-Devel Archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Ross Lagerwall <ross.lagerwall@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH v3] tools/libxc: Batch memory allocations for PV guests
Date: Wed, 17 Jun 2015 12:14:03 +0100	[thread overview]
Message-ID: <1434539643.13744.326.camel@citrix.com> (raw)
In-Reply-To: <20150615160837.GG10177@zion.uk.xensource.com>

On Mon, 2015-06-15 at 17:08 +0100, Wei Liu wrote:
> On Mon, Jun 15, 2015 at 11:12:07AM +0100, Ross Lagerwall wrote:
> > The current code for allocating memory for PV guests batches the
> > hypercalls to allocate memory by allocating 1024*1024 extents of order 0
> > at a time. To make this faster, first try allocating extents of order 9
> > (2 MiB) before falling back to the order 0 allocating if the order 9
> > allocation fails.
> > 
> > On my test machine this reduced the time to start a 128 GiB PV guest by
> > about 60 seconds.

>From 61s or from 600s?

> > 
> > Signed-off-by: Ross Lagerwall <ross.lagerwall@citrix.com>
> 
> Acked-by: Wei Liu <wei.liu2@citrix.com>

Applied. There were some rejects due to "libxc: unify handling of vNUMA
layout" having gone in first, I think they were just contextual and they
seemed trivial to resolve, but please do (both) check.

Ian.

  reply	other threads:[~2015-06-17 11:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 10:12 [PATCH v3] tools/libxc: Batch memory allocations for PV guests Ross Lagerwall
2015-06-15 16:08 ` Wei Liu
2015-06-17 11:14   ` Ian Campbell [this message]
2015-06-17 11:22     ` Ross Lagerwall
2015-06-17 11:40       ` Ian Campbell
2015-06-17 11:24     ` Wei Liu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1434539643.13744.326.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=ross.lagerwall@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).