From: George Dunlap <george.dunlap@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 0 of 4] RESEND Use superpages on restore/migrate
Date: Wed, 25 May 2011 14:56:37 +0100 [thread overview]
Message-ID: <1306331797.21026.8515.camel@elijah> (raw)
In-Reply-To: <19931.60196.141220.28108@mariner.uk.xensource.com>
On Tue, 2011-05-24 at 18:30 +0100, Ian Jackson wrote:
> George Dunlap writes ("[Xen-devel] [PATCH 0 of 4] RESEND Use superpages on restore/migrate"):
> > This patch series restores the use of superpages when restoring or
> > migrating a VM, while retaining efficient batching of 4k pages when
> > superpages are not appropriate or available.
>
> Thanks for this. It looks plausible but I haven't done a detailed
> review.
>
> Given how much other stuff I've thrown in today I'll at least wait to
> see what the tests look like and consider applying this tomorrow.
Ack. FWIW it's been through a week of XenRT runs with Boston without
noticeable incident.
-George
next prev parent reply other threads:[~2011-05-25 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 10:51 [PATCH 0 of 4] RESEND Use superpages on restore/migrate George Dunlap
2011-05-16 10:51 ` [PATCH 1 of 4] tools: Detect superpages on domain restore George Dunlap
2011-05-16 10:51 ` [PATCH 2 of 4] tools: Save superpages in the same batch, to make detection easier George Dunlap
2011-05-16 10:51 ` [PATCH 3 of 4] tools: Introduce "allocate-only" page type for migration George Dunlap
2011-05-16 10:51 ` [PATCH 4 of 4] tools: Enable superpages for HVM domains by default George Dunlap
2011-05-24 17:30 ` [PATCH 0 of 4] RESEND Use superpages on restore/migrate Ian Jackson
2011-05-25 13:56 ` George Dunlap [this message]
2011-05-26 14:28 ` Ian Jackson
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=1306331797.21026.8515.camel@elijah \
--to=george.dunlap@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 NNTP newsgroup(s).