From: Paolo Bonzini <pbonzini@redhat.com>
To: "Wangting (Kathy)" <kathy.wangting@huawei.com>
Cc: "zhangmin (S)" <zhangmin6@huawei.com>,
Juan Quintela <quintela@redhat.com>,
Luonengjun <luonengjun@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Stefan Weil <stefan.weil@weilnetz.de>,
"Chentao (Boby)" <boby.chen@huawei.com>,
"Wangrui (K)" <moon.wangrui@huawei.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Qinling <mail.qinling@huawei.com>,
"Wubin (H)" <wu.wubin@huawei.com>
Subject: Re: [Qemu-devel] [PATCH for-1.7?] the calculation of bytes_xfer in qemu_put_buffer() is wrong
Date: Wed, 20 Nov 2013 11:37:55 +0100 [thread overview]
Message-ID: <528C9103.9050608@redhat.com> (raw)
In-Reply-To: <F5FDBD9C42529D44A051B02D2563D520562849C0@szxema505-mbx.china.huawei.com>
Il 20/11/2013 06:28, Wangting (Kathy) ha scritto:
> Hi Paolo and Stefan,
>
> I am really sorry for my email before that I didn't say clearly about
> the bug fix.
>
> f->bytes_xfer means the number of bytes which is send from source to
> destination during the migration. It is limited by the f->xfer_limit
> which is converted from bandwidth. That means if bytes_xfer is larger
> than the limit, the current iteration will not do block and memory
> migration util the next iteration.
>
> But in function qemu_put_buffer, the statistics is wrong. The size of
> block migration is 1MB for each block, but the buffer size for
> sending is IO_BUF_SIZE(32768bytes). When it need to be send, 1MB
> block will be divided into small trunks, so f->bytes_xfer should be
> increased by the size of the small trunks every time which is
> actually send, in function qemu_put_buffer it should be the variable
> "l".
>
> Otherwise, f->bytes_xfer will be increased by (small trunks number *
> 1MB) while sending 1MB block, it is much larger than the size which
> is actually send, and it will soon be reached to the size of
> f->xfer_limit, so the current iteration will send less data blocks
> than expected.
>
> If you have any questions, please let me know, thank you very much.
Thank you very much. Juan, I guess you need to prepare another pull
request.
Paolo
next prev parent reply other threads:[~2013-11-20 10:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 5:53 [Qemu-devel] [PATCH] the calculation of bytes_xfer in qemu_put_buffer() is wrong Wangting (Kathy)
2013-11-19 8:19 ` Paolo Bonzini
2013-11-19 17:55 ` [Qemu-devel] [PATCH for-1.7?] " Stefan Weil
2013-11-19 18:07 ` Paolo Bonzini
2013-11-20 5:28 ` Wangting (Kathy)
2013-11-20 10:37 ` Paolo Bonzini [this message]
2013-11-20 11:27 ` [Qemu-devel] [PATCH] " Juan Quintela
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=528C9103.9050608@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=boby.chen@huawei.com \
--cc=kathy.wangting@huawei.com \
--cc=luonengjun@huawei.com \
--cc=mail.qinling@huawei.com \
--cc=moon.wangrui@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefan.weil@weilnetz.de \
--cc=wu.wubin@huawei.com \
--cc=zhangmin6@huawei.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 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).