From: Eric Blake <eblake@redhat.com>
To: jemmy858585@gmail.com, stefanha@redhat.com, famz@redhat.com,
quintela@redhat.com, dgilbert@redhat.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] migration/block: Avoid involve into blk_drain too frequently
Date: Tue, 14 Mar 2017 10:12:30 -0500 [thread overview]
Message-ID: <420d9095-bde2-6573-e883-ab6b57d4a860@redhat.com> (raw)
In-Reply-To: <1489478243-10366-1-git-send-email-jemmy858585@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
On 03/14/2017 02:57 AM, jemmy858585@gmail.com wrote:
> From: Lidong Chen <jemmy858585@gmail.com>
>
> Increase bmds->cur_dirty after submit io, so reduce the frequency involve into blk_drain, and improve the performance obviously when block migration.
Long line; please wrap your commit messages, preferably around 70 bytes
since 'git log' displays them indented, and it is still nice to read
them in an 80-column window.
Do you have benchmark numbers to prove the impact of this patch, or even
a formula for reproducing the benchmark testing?
>
> Signed-off-by: Lidong Chen <jemmy858585@gmail.com>
> ---
> migration/block.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/migration/block.c b/migration/block.c
> index 6741228..f059cca 100644
> --- a/migration/block.c
> +++ b/migration/block.c
> @@ -576,6 +576,8 @@ static int mig_save_device_dirty(QEMUFile *f, BlkMigDevState *bmds,
> }
>
> bdrv_reset_dirty_bitmap(bmds->dirty_bitmap, sector, nr_sectors);
> + sector += nr_sectors;
> + bmds->cur_dirty = sector;
> break;
> }
> sector += BDRV_SECTORS_PER_DIRTY_CHUNK;
>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-03-14 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 7:57 [Qemu-devel] [PATCH] migration/block: Avoid involve into blk_drain too frequently jemmy858585
2017-03-14 15:12 ` Eric Blake [this message]
2017-03-14 15:15 ` Eric Blake
2017-03-15 2:34 ` 858585 jemmy
2017-03-15 2:28 ` 858585 jemmy
2017-03-15 2:57 ` Fam Zheng
2017-03-15 3:11 ` 858585 jemmy
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=420d9095-bde2-6573-e883-ab6b57d4a860@redhat.com \
--to=eblake@redhat.com \
--cc=dgilbert@redhat.com \
--cc=famz@redhat.com \
--cc=jemmy858585@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@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 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).