qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@openvz.org>
To: Jeff Cody <jcody@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
	Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] mirror: fix improperly filled copy_bitmap for mirror block job
Date: Wed, 7 Sep 2016 09:54:29 +0300	[thread overview]
Message-ID: <97fdfac5-43c3-334e-31d4-d728f56b4640@openvz.org> (raw)
In-Reply-To: <20160907061544.GA1917@localhost.localdomain>

On 09/07/2016 09:15 AM, Jeff Cody wrote:
> On Tue, Sep 06, 2016 at 06:11:19PM +0300, Denis V. Lunev wrote:
>> bdrv_is_allocated_above() returns true in the case if qcow2 even for
>> completely zeroed areas as BDRV_BLOCK_ALLOCATED flag is set in both
>> cases.
> Hi Denis,
>
> Not just qcow2.  BDRV_BLOCK_ALLOCATED for a layer means the content of the
> block is defined by that layer (even if that is a zero block, that doesn't
> mean it is unallocated).  This applies to all image formats.
>
>> Though we have completely zeroed out the image just above or it was
>> already zeroed.
> This is only true if we are in 'sync = full' mode.
>
>> The patch stops using bdrv_is_allocated_above() wrapper and switches to
>> bdrv_get_block_status_above() to distinguish zeroed areas and areas with
>> data to avoid extra IO operations, which could be VERY slow.
> For 'sync = top', we need to make sure to appropriately allocate the sector,
> even if it is BDRV_BLOCK_ZERO.
>
>> Signed-off-by: Denis V. Lunev <den@openvz.org>
>> CC: Jeff Cody <jcody@redhat.com>
>> CC: Kevin Wolf <kwolf@redhat.com>
>> CC: Max Reitz <mreitz@redhat.com>
>> ---
>>  block/mirror.c | 13 ++++++++-----
>>  1 file changed, 8 insertions(+), 5 deletions(-)
>>
>> diff --git a/block/mirror.c b/block/mirror.c
>> index e0b3f41..87edbd8 100644
>> --- a/block/mirror.c
>> +++ b/block/mirror.c
>> @@ -552,7 +552,7 @@ static int coroutine_fn mirror_dirty_init(MirrorBlockJob *s)
>>      BlockDriverState *base = s->base;
>>      BlockDriverState *bs = blk_bs(s->common.blk);
>>      BlockDriverState *target_bs = blk_bs(s->target);
>> -    int ret, n;
>> +    int n;
>>  
>>      end = s->bdev_length / BDRV_SECTOR_SIZE;
>>  
>> @@ -590,6 +590,8 @@ static int coroutine_fn mirror_dirty_init(MirrorBlockJob *s)
>>          /* Just to make sure we are not exceeding int limit. */
>>          int nb_sectors = MIN(INT_MAX >> BDRV_SECTOR_BITS,
>>                               end - sector_num);
>> +        int64_t status;
>> +        BlockDriverState *file;
>>  
>>          mirror_throttle(s);
>>  
>> @@ -597,13 +599,14 @@ static int coroutine_fn mirror_dirty_init(MirrorBlockJob *s)
>>              return 0;
>>          }
>>  
>> -        ret = bdrv_is_allocated_above(bs, base, sector_num, nb_sectors, &n);
>> -        if (ret < 0) {
>> -            return ret;
>> +        status = bdrv_get_block_status_above(bs, base, sector_num,
>> +                                             nb_sectors, &n, &file);
>> +        if (status < 0) {
>> +            return status;
>>          }
>>  
>>          assert(n > 0);
>> -        if (ret == 1) {
>> +        if (status & BDRV_BLOCK_DATA) {
> I think this patch would work if this was changed to something like this:
>
>          mark_dirty = base == NULL ? status & BDRV_BLOCK_DATA :     /* 'full' */
>                                      status & BDRV_BLOCK_ALLOCATED;
>
>          if (mark_dirty) {
reasonable. I have doubts with the code but was unable to
formulate. Thank you for clarifications. Will respin.

Den

      reply	other threads:[~2016-09-07  9:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06 15:11 [Qemu-devel] [PATCH 1/1] mirror: fix improperly filled copy_bitmap for mirror block job Denis V. Lunev
2016-09-07  6:15 ` Jeff Cody
2016-09-07  6:54   ` Denis V. Lunev [this message]

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=97fdfac5-43c3-334e-31d4-d728f56b4640@openvz.org \
    --to=den@openvz.org \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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).