From: Peter Lieven <pl@dlhnet.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] big wait check in ram_save_iterate()
Date: Sat, 15 Dec 2012 12:20:18 +0100 [thread overview]
Message-ID: <50CC5CF2.2040606@dlhnet.de> (raw)
In-Reply-To: <1941762316.24986459.1355562148249.JavaMail.root@redhat.com>
Am 15.12.2012 10:02, schrieb Paolo Bonzini:
>
>> is the check for spending > 50ms in the loop still necessary in qemu
>> 1.3.0?
>
> Yes, it helps finding the available bandwidth and tuning the downtime of
> migration.
Aha, okay. But then it should also be added to block migration, shoudn't it?
I tested it in qemu-kvm 1.2.0 and it help to increase responsiveness if the
I/O latency on the storage is high.
Peter
>
> Paolo
>
next prev parent reply other threads:[~2012-12-15 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 18:14 [Qemu-devel] big wait check in ram_save_iterate() Peter Lieven
2012-12-15 9:02 ` Paolo Bonzini
2012-12-15 11:20 ` Peter Lieven [this message]
2012-12-16 14:05 ` Paolo Bonzini
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=50CC5CF2.2040606@dlhnet.de \
--to=pl@dlhnet.de \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 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.