From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: aliguori@us.ibm.com, Dor Laor <dlaor@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] augment info migrate with page status
Date: Thu, 21 May 2009 17:40:19 +0300 [thread overview]
Message-ID: <4A1567D3.2090902@redhat.com> (raw)
In-Reply-To: <20090521135218.GA24584@poweredge.glommer>
Glauber Costa wrote:
>> Alternately it can be parametrized by the monitor command.
>>
> With this, I completely disagree. Let us say we switch in the future to a
> new migration algorithm that does not rely on any treshold at all. What
> should we do with this parameter?
>
> This is totally implementation dependant, and should not be exposed.
> the bandwidth is what we want to control externally.
>
We want to control bandwidth and application downtime. Why not specify
those as parameters?
qemu will live migrate using the specified bandwidth until it reaches a
page count that allows it to stop the guest and complete migration
within the allowed downtime.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-05-21 14:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 23:20 [Qemu-devel] [PATCH] augment info migrate with page status Glauber Costa
2009-05-21 10:22 ` Dor Laor
2009-05-21 13:14 ` Anthony Liguori
2009-05-21 13:52 ` Glauber Costa
2009-05-21 14:40 ` Avi Kivity [this message]
2009-05-21 14:05 ` Daniel P. Berrange
2009-05-21 14:20 ` Glauber Costa
2009-05-21 14:58 ` Avi Kivity
2009-05-21 15:04 ` Daniel P. Berrange
2009-05-21 16:07 ` Glauber Costa
2009-05-21 23:41 ` [Qemu-devel] QEMU Official OS Support PAge Natalia Portillo
-- strict thread matches above, loose matches on Subject: below --
2009-05-21 18:26 [Qemu-devel] [PATCH] augment info migrate with page status Glauber Costa
2009-05-21 19:17 Glauber Costa
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=4A1567D3.2090902@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=dlaor@redhat.com \
--cc=glommer@redhat.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 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.