qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Chentao (Boby)" <boby.chen@huawei.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
	"Wangting (Kathy)" <kathy.wangting@huawei.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Qinling <mail.qinling@huawei.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"Zhangmin (Rudy)" <rudy.zhangmin@huawei.com>,
	"Wubin (H)" <wu.wubin@huawei.com>
Subject: Re: [Qemu-devel] [PATCH] drive-mirror: Change the amount of data base on granularity
Date: Mon, 24 Feb 2014 14:20:23 +0100	[thread overview]
Message-ID: <20140224132023.GC15488@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <93A91DC620F1514FB39E878E5131C8CF0E3607FF@nkgeml511-mbx.china.huawei.com>

On Sat, Jan 18, 2014 at 08:09:43AM +0000, Chentao (Boby) wrote:

Please CC Kevin Wolf <kwolf@redhat.com> who co-maintains the QEMU block
layer with me.  Use scripts/get_maintainer.pl -f block/mirror.c to find
the list of maintainers to CC.

> Before, one iteration send the amount of data is continuous dirty block, maximum is mirror buffer size(default is 10M).
> 
> This way has a low write/read performance. If image type is raw, first loop, all the data is dirty.
> 
> One iteration, read 10M data and then write 10M data to target image, so read and write cannot be parallelized.
> 
> 
> 
> Now, I change the amount of data in an iteration, it base on granularity. We can set the granularity to 1M,so it can send
> 
> 10 times read request, and then send write request. Once a write request is done, it will have 1M free buffer to send next read request.
> 
> So this way can allow read/write to be parallelized.
> 
> 
> 
> This change can improve read and write performance.
> 
> On my server:
> 
> (write) MBps:55MB/S --> 90 MB/S utility:50%->85%
> 
> 
> 
> Signed-off-by: Zhang Min <rudy.zhangmin@huawei.com<mailto:rudy.zhangmin@huawei.com>>
> 

This patch is not signed off by you.  If you have permission to
contribute this patch on behalf of Zhang Min, please add your own
Signed-off-by: below.

Please also remove the <mailto:> link.  It should just be:
First Last <username@domain.com>

> ---
> 
> block/mirror.c |   68 ++++++++++++++++++++++---------------------------------
> 
> 1 files changed, 27 insertions(+), 41 deletions(-)
> 
> 
> 
> diff --git a/block/mirror.c b/block/mirror.c index 2932bab..1ba2862 100644
> 
> --- a/block/mirror.c

Please do not send patches with Outlook or in HTML.  Use
git-send-email(1) to send patches that are properly formatted and can be
applied with git-am(1) by the maintainers.

For more info on patch submission guidelines, please see:
http://qemu-project.org/Contribute/SubmitAPatch

I have reformatted the remainder of this email.

> +++ b/block/mirror.c
> @@ -183,54 +183,40 @@ static void coroutine_fn mirror_iteration(MirrorBlockJob *s)
>          qemu_coroutine_yield();
>      }
> 
> -    do {
> -        int added_sectors, added_chunks;
> +    int added_sectors, added_chunks;
> 
> -        if (!bdrv_get_dirty(source, s->dirty_bitmap, next_sector) ||
> -            test_bit(next_chunk, s->in_flight_bitmap)) {
> -            assert(nb_sectors > 0);
> -            break;
> -        }
> +    added_sectors = sectors_per_chunk;
> +    if (s->cow_bitmap && !test_bit(next_chunk, s->cow_bitmap)) {
> +        bdrv_round_to_clusters(s->target,
> +                next_sector, added_sectors,
> +                &next_sector, &added_sectors);
> 
> -        added_sectors = sectors_per_chunk;
> -        if (s->cow_bitmap && !test_bit(next_chunk, s->cow_bitmap)) {
> -            bdrv_round_to_clusters(s->target,
> -                                   next_sector, added_sectors,
> -                                   &next_sector, &added_sectors);
> -
> -            /* On the first iteration, the rounding may make us copy
> -             * sectors before the first dirty one.
> -             */
> -            if (next_sector < sector_num) {
> -                assert(nb_sectors == 0);
> -                sector_num = next_sector;
> -                next_chunk = next_sector / sectors_per_chunk;
> -            }
> +        /* On the first iteration, the rounding may make us copy
> +         * sectors before the first dirty one.
> +         */
> +        if (next_sector < sector_num) {
> +            assert(nb_sectors == 0);
> +            sector_num = next_sector;
> +            next_chunk = next_sector / sectors_per_chunk;
>          }
> +    }
> 
> -        added_sectors = MIN(added_sectors, end - (sector_num + nb_sectors));
> -        added_chunks = (added_sectors + sectors_per_chunk - 1) / sectors_per_chunk;
> +    added_sectors = MIN(added_sectors, end - (sector_num + nb_sectors));
> +    added_chunks = (added_sectors + sectors_per_chunk - 1) /
> + sectors_per_chunk;
> 
> -        /* When doing COW, it may happen that there is not enough space for
> -         * a full cluster.  Wait if that is the case.
> -         */
> -        while (nb_chunks == 0 && s->buf_free_count < added_chunks) {
> -            trace_mirror_yield_buf_busy(s, nb_chunks, s->in_flight);
> -            qemu_coroutine_yield();
> -        }
> -        if (s->buf_free_count < nb_chunks + added_chunks) {
> -            trace_mirror_break_buf_busy(s, nb_chunks, s->in_flight);
> -            break;
> -        }
> +    /* When doing COW, it may happen that there is not enough space for
> +     * a full cluster.  Wait if that is the case.
> +     */
> +    while (nb_chunks == 0 && s->buf_free_count < added_chunks) {
> +        trace_mirror_yield_buf_busy(s, nb_chunks, s->in_flight);
> +        qemu_coroutine_yield();
> +    }
> 
> -        /* We have enough free space to copy these sectors.  */
> -        bitmap_set(s->in_flight_bitmap, next_chunk, added_chunks);
> +    /* We have enough free space to copy these sectors.  */
> +    bitmap_set(s->in_flight_bitmap, next_chunk, added_chunks);
> 
> -        nb_sectors += added_sectors;
> -        nb_chunks += added_chunks;
> -        next_sector += added_sectors;
> -        next_chunk += added_chunks;
> -    } while (next_sector < end);
> +    nb_sectors += added_sectors;
> +    nb_chunks += added_chunks;

I think further discussion will be required, this patch undoes something
that the code is designed to do.  You forgot to modify the big block
comment above this code that explains that we are trying to extend the
copy region to be at least one cluster and also to cover adjacent dirty
blocks (to reduce the number of I/O requests).

I have CCed Paolo Bonzini, who implemented most of block/mirror.c.
Maybe he can discuss the purpose of this change with you.

  reply	other threads:[~2014-02-24 13:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-18  8:09 [Qemu-devel] [PATCH] drive-mirror: Change the amount of data base on granularity Chentao (Boby)
2014-02-24 13:20 ` Stefan Hajnoczi [this message]
2014-02-24 13:36   ` 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=20140224132023.GC15488@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=boby.chen@huawei.com \
    --cc=famz@redhat.com \
    --cc=kathy.wangting@huawei.com \
    --cc=kwolf@redhat.com \
    --cc=mail.qinling@huawei.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rudy.zhangmin@huawei.com \
    --cc=wu.wubin@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).