qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Charlie Shepherd <charlie@ctshepherd.com>
Cc: kwolf@redhat.com, stefanha@gmail.com, gabriel@kerneis.info,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 3/3] COW: Skip setting already set bits
Date: Wed, 06 Nov 2013 14:03:35 +0100	[thread overview]
Message-ID: <527A3E27.3050705@redhat.com> (raw)
In-Reply-To: <1383742617-14742-4-git-send-email-charlie@ctshepherd.com>

Il 06/11/2013 13:56, Charlie Shepherd ha scritto:
> Rather than unnecessarily setting bits that are already set, re-use cow_find_streak to find how
> many bits are already set for this sector, and only set unset bits. Do this before the flush to
> avoid it if no bits need to be set at all.
> 
> Signed-off-by: Charlie Shepherd <charlie@ctshepherd.com>
> ---
>  block/cow.c | 12 ++++++++++--
>  1 file changed, 10 insertions(+), 2 deletions(-)
> 
> diff --git a/block/cow.c b/block/cow.c
> index 41097d8..93207eb 100644
> --- a/block/cow.c
> +++ b/block/cow.c
> @@ -203,7 +203,7 @@ static int cow_update_bitmap(BlockDriverState *bs, int64_t sector_num,
>      bool first = true;
>  
>      while (nb_sectors) {

You still need to make this a "for" and put "offset += BDRV_SECTOR_SIZE"
in the third clause.

> -        int ret;
> +        int ret, set;
>          uint8_t bitmap[BDRV_SECTOR_SIZE];
>  
>          bitnum &= BITS_PER_BITMAP_SECTOR - 1;
> @@ -214,6 +214,15 @@ static int cow_update_bitmap(BlockDriverState *bs, int64_t sector_num,
>              return ret;
>          }
>  
> +        /* Skip over any already set bits */
> +        set = cow_find_streak(bitmap, 1, bitnum, sector_bits);
> +        bitnum += set;
> +        sector_bits -= set;
> +        nb_sectors -= set;
> +        if (set == sector_bits) {
> +            continue;
> +        }

This now has to be "if (set == 0)".  With the change to the "for" above,
that's correct.

>          if (first) {
>              ret = bdrv_flush(bs->file);
>              if (ret < 0) {
> @@ -228,7 +237,6 @@ static int cow_update_bitmap(BlockDriverState *bs, int64_t sector_num,
>          if (ret < 0) {
>              return ret;
>          }
> -
>          bitnum += sector_bits;
>          nb_sectors -= sector_bits;
>          offset += BDRV_SECTOR_SIZE;
> 

I also noticed that patch 1 introduces a small regression, in that it
will always flush data even if the metadata doesn't change.  This patch
fixes it, because the "bdrv_flush" is preceded by the check to skip over
any already set bits.

So I suggest that, together with the above fixes, you squash patches 1
and 3 together.

Paolo

  reply	other threads:[~2013-11-06 13:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 12:56 [Qemu-devel] [PATCH v2 0/3] COW: Speed up writes Charlie Shepherd
2013-11-06 12:56 ` [Qemu-devel] [PATCH v2 1/3] " Charlie Shepherd
2013-11-06 12:56 ` [Qemu-devel] [PATCH v2 2/3] COW: Extend checking allocated bits to beyond one sector Charlie Shepherd
2013-11-06 12:56 ` [Qemu-devel] [PATCH v2 3/3] COW: Skip setting already set bits Charlie Shepherd
2013-11-06 13:03   ` Paolo Bonzini [this message]
2013-11-06 13:07     ` Charlie Shepherd

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=527A3E27.3050705@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=charlie@ctshepherd.com \
    --cc=gabriel@kerneis.info \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).