From: Kevin Wolf <kwolf@redhat.com>
To: Lidong Chen <jemmy858585@gmail.com>
Cc: qemu-devel@nongnu.org, famz@redhat.com, qemu-block@nongnu.org,
quintela@redhat.com, dgilbert@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v2] migration/block: Avoid invoking blk_drain too frequently
Date: Wed, 15 Mar 2017 11:21:36 +0100 [thread overview]
Message-ID: <20170315102136.GD4030@noname.str.redhat.com> (raw)
In-Reply-To: <1489549053-31728-1-git-send-email-jemmy858585@gmail.com>
Am 15.03.2017 um 04:37 hat Lidong Chen geschrieben:
> Increase bmds->cur_dirty after submit io, so reduce the frequency
> involve into blk_drain, and improve the performance obviously
> when block migration.
>
> The performance test result of this patch:
>
> During the block dirty save phase, this patch improve guest os IOPS
> from 4.0K to 9.5K. and improve the migration speed from
> 505856 rsec/s to 855756 rsec/s.
>
> Signed-off-by: Lidong Chen <jemmy858585@gmail.com>
> ---
> migration/block.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/migration/block.c b/migration/block.c
> index 6741228..7734ff7 100644
> --- a/migration/block.c
> +++ b/migration/block.c
> @@ -576,6 +576,9 @@ static int mig_save_device_dirty(QEMUFile *f, BlkMigDevState *bmds,
> }
>
> bdrv_reset_dirty_bitmap(bmds->dirty_bitmap, sector, nr_sectors);
> + sector += nr_sectors;
sector += BDRV_SECTORS_PER_DIRTY_CHUNK would be acceptable here...
> + bmds->cur_dirty = sector;
> +
> break;
> }
> sector += BDRV_SECTORS_PER_DIRTY_CHUNK;
> bmds->cur_dirty = sector;
> }
...which would make it the same code as the rest of the loop. It could
be nicer to reuse the same code and just set a bool when a request is
submitted so that the loop terminates after that.
But that's just a matter of taste, so I'll still give:
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
next prev parent reply other threads:[~2017-03-15 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 3:37 [Qemu-devel] [PATCH v2] migration/block: Avoid invoking blk_drain too frequently Lidong Chen
2017-03-15 10:21 ` Kevin Wolf [this message]
2017-03-15 11:10 ` Fam Zheng
2017-03-15 17:31 ` Dr. David Alan Gilbert
2017-03-16 1:33 ` Fam Zheng
2017-03-16 7:59 ` 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=20170315102136.GD4030@noname.str.redhat.com \
--to=kwolf@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).