From: Kevin Wolf <kwolf@redhat.com>
To: Avishay Traeger <AVISHAY@il.ibm.com>
Cc: qemu-devel@nongnu.org, Liran Schour <LIRANS@il.ibm.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2] Improve accuracy of block migration bandwidth calculation
Date: Wed, 20 Apr 2011 14:34:49 +0200 [thread overview]
Message-ID: <4DAED2E9.3030708@redhat.com> (raw)
In-Reply-To: <OFB6BB9DCC.7838F587-ONC2257867.002AF477-C2257867.002ED7B5@il.ibm.com>
Am 03.04.2011 10:31, schrieb Avishay Traeger:
>
> Revised patch for improving the accuracy of the block migration bandwidth
> calculation. Thanks a lot to Michael Roth for the input.
>
> For those that missed the original patch, here is the description:
> block_mig_state.total_time is currently the sum of the read request
> latencies. This is not very accurate because block migration uses aio and
> so several requests can be submitted at once. Bandwidth should be computed
> with wall-clock time, not by adding the latencies. In this case,
> "total_time" has a higher value than it should, and so the computed
> bandwidth is lower than it is in reality. This means that migration can
> take longer than it needs to.
> However, we don't want to use pure wall-clock time here. We are computing
> bandwidth in the asynchronous phase, where the migration repeatedly wakes
> up and sends some aio requests. The computed bandwidth will be used for
> synchronous transfer.
>
>
> Avishay
>
>
> Signed-off-by: Avishay Traeger <avishay@il.ibm.com>
Thanks. Fixed line wraps and coding style and applied to the block
branch. Please take care to avoid patch corruption next time - usually
such patches are not fixed manually, but rejected.
Kevin
prev parent reply other threads:[~2011-04-20 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 8:31 [Qemu-devel] [PATCH v2] Improve accuracy of block migration bandwidth calculation Avishay Traeger
2011-04-05 18:20 ` [Qemu-devel] " Michael Roth
2011-04-20 12:34 ` Kevin Wolf [this message]
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=4DAED2E9.3030708@redhat.com \
--to=kwolf@redhat.com \
--cc=AVISHAY@il.ibm.com \
--cc=LIRANS@il.ibm.com \
--cc=mdroth@linux.vnet.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).