From: Olaf Hering <olaf@aepfle.de>
To: Keir Fraser <keir.xen@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: reliable live migration of large and busy guests
Date: Tue, 6 Nov 2012 23:18:06 +0100 [thread overview]
Message-ID: <20121106221806.GA1813@aepfle.de> (raw)
In-Reply-To: <CCBF2785.442DA%keir.xen@gmail.com>
On Tue, Nov 06, Keir Fraser wrote:
> It's known that if you have a workload that is dirtying lots of pages
> quickly, the final stop-and-copy phase will necessarily be large. A VM that
> is busy dirtying lots of pages can dirty pages much quicker than they can be
> transferred over the LAN.
In my opinion such migration should be done at application level.
> > Should 'xm migrate --live' and 'xl migrate' get something like a
> > --no-suspend option?
>
> Well, it is not really possible to avoid the suspend altogether, there is
> always going to be some minimal 'dirty working set'. But could provide
> parameters to require the dirty working set to be smaller than X pages
> within Y rounds of dirty page copying.
Should such knobs be exposed to the tools like x[lm] migrate --knob1 val --knob2 val?
Olaf
next prev parent reply other threads:[~2012-11-06 22:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 20:28 reliable live migration of large and busy guests Olaf Hering
2012-11-06 20:45 ` Keir Fraser
2012-11-06 22:18 ` Olaf Hering [this message]
2012-11-06 23:18 ` Andrew Cooper
2012-11-06 23:41 ` Dan Magenheimer
2012-11-07 13:44 ` Andrew Cooper
2012-11-07 15:10 ` Dan Magenheimer
2012-11-08 10:58 ` George Dunlap
2012-11-12 17:12 ` Dan Magenheimer
2012-11-07 14:13 ` Olaf Hering
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=20121106221806.GA1813@aepfle.de \
--to=olaf@aepfle.de \
--cc=keir.xen@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.