From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Amit Shah <amit.shah@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] migration: Increase default max_downtime from 30ms to 300ms
Date: Sat, 07 Jun 2014 02:48:14 +1000 [thread overview]
Message-ID: <5391F0CE.5040304@ozlabs.ru> (raw)
In-Reply-To: <20140606125036.GB27148@grmbl.mre>
On 06/06/2014 10:50 PM, Amit Shah wrote:
> On (Thu) 27 Mar 2014 [14:57:26], Alexey Kardashevskiy wrote:
>> The existing timeout is 30ms which on 100MB/s (1Gbit) gives us
>> 3MB/s rate maximum. If we put some load on the guest, it is easy to
>> get page dirtying rate too big so live migration will never complete.
>> In the case of libvirt that means that the guest will be stopped
>> anyway after a timeout specified in the "virsh migrate" command and
>> this normally generates even bigger delay.
>>
>> This changes max_downtime to 300ms which seems to be more
>> reasonable value.
>>
>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>
> Reviewed-by: Amit Shah <amit.shah@redhat.com>
Cool, thanks!
But what is next? The patch is > 2 months old and it is simple and
everything but it did not make it to any tree so far :)
--
Alexey
next prev parent reply other threads:[~2014-06-06 16:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 3:57 [Qemu-devel] [PATCH] migration: Increase default max_downtime from 30ms to 300ms Alexey Kardashevskiy
2014-03-27 9:01 ` Markus Armbruster
[not found] ` <53494FD0.8020009@ozlabs.ru>
[not found] ` <53604D73.1040905@ozlabs.ru>
2014-05-05 9:17 ` Alexey Kardashevskiy
2014-05-05 11:20 ` Juan Quintela
2014-06-04 8:13 ` Alexey Kardashevskiy
2014-06-04 10:25 ` Juan Quintela
2014-06-04 10:26 ` Paolo Bonzini
2014-06-06 12:50 ` Amit Shah
2014-06-06 16:48 ` Alexey Kardashevskiy [this message]
2014-06-09 5:22 ` Amit Shah
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=5391F0CE.5040304@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@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.