From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel@nongnu.org, Liran Schour <lirans@il.ibm.com>
Subject: Re: [Qemu-devel] Re: [PATCH 4/4] Try not to exceed max downtime on stage3
Date: Tue, 12 Jan 2010 09:07:17 -0600 [thread overview]
Message-ID: <4B4C9025.10409@codemonkey.ws> (raw)
In-Reply-To: <4B4C622D.5040800@siemens.com>
On 01/12/2010 05:51 AM, Jan Kiszka wrote:
> Liran Schour wrote:
>
>> Move to stage3 only when remaining work can be done below max downtime.
>> To make sure the process will converge we will try only MAX_DIRTY_ITERATIONS.
>>
> OK, that explains now patch 2. But do we have such barrier for memory
> migration as well?
No, we explicitly don't because making that decision is a management
tool job.
A management tool can force convergence by explicitly stopping the guest.
Iterations is a bad metric because there's no real useful meaning to a user.
Time is probably the best metric and it's easy for a management tool to
set a timer to stop the guest if it hasn't completed by a certain time
period.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-01-12 15:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 8:27 [Qemu-devel] [PATCH 0/4] Reduce down time during migration without shared storage Liran Schour
2010-01-12 8:27 ` [Qemu-devel] [PATCH 1/4] Remove unused code Liran Schour
2010-01-12 8:27 ` [Qemu-devel] [PATCH 2/4] Tranfer dirty blocks during iterative phase Liran Schour
2010-01-12 8:27 ` [Qemu-devel] [PATCH 3/4] Count dirty blocks and expose an API to get dirty count Liran Schour
2010-01-12 8:27 ` [Qemu-devel] [PATCH 4/4] Try not to exceed max downtime on stage3 Liran Schour
2010-01-12 9:52 ` Pierre Riteau
2010-01-12 11:56 ` Liran Schour
2010-01-12 11:51 ` [Qemu-devel] " Jan Kiszka
2010-01-12 15:07 ` Anthony Liguori [this message]
2010-01-12 15:07 ` Liran Schour
2010-01-12 11:50 ` [Qemu-devel] Re: [PATCH 3/4] Count dirty blocks and expose an API to get dirty count Jan Kiszka
2010-01-12 11:50 ` [Qemu-devel] Re: [PATCH 2/4] Tranfer dirty blocks during iterative phase Jan Kiszka
2010-01-12 11:50 ` [Qemu-devel] Re: [PATCH 1/4] Remove unused code Jan Kiszka
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=4B4C9025.10409@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--cc=lirans@il.ibm.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).