qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Reda Sallahi <fullmanet@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
	Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] vmdk: fix metadata write regression
Date: Thu, 7 Jul 2016 16:54:38 +0800	[thread overview]
Message-ID: <20160707085438.GB12042@ad.usersys.redhat.com> (raw)
In-Reply-To: <20160707084249.29084-1-fullmanet@gmail.com>

On Thu, 07/07 10:42, Reda Sallahi wrote:
> Commit "cdeaf1f vmdk: add bdrv_co_write_zeroes" causes a regression on
> writes. It writes metadata after every write instead of doing it only once
> for each cluster.
> 
> vmdk_pwritev() writes metadata whenever m_data is set as valid so this patch
> sets m_data as valid only when we have a new cluster which hasn't been
> allocated before or a zero grain.
> 
> Signed-off-by: Reda Sallahi <fullmanet@gmail.com>
> ---
> v2: Corrected the commit id referenced in the commit message.
> 
>  block/vmdk.c | 14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/block/vmdk.c b/block/vmdk.c
> index d73f431..1cbd487 100644
> --- a/block/vmdk.c
> +++ b/block/vmdk.c
> @@ -1202,13 +1202,6 @@ static int get_cluster_offset(BlockDriverState *bs,
>      l2_index = ((offset >> 9) / extent->cluster_sectors) % extent->l2_size;
>      cluster_sector = le32_to_cpu(l2_table[l2_index]);
>  
> -    if (m_data) {
> -        m_data->valid = 1;
> -        m_data->l1_index = l1_index;
> -        m_data->l2_index = l2_index;
> -        m_data->l2_offset = l2_offset;
> -        m_data->l2_cache_entry = &l2_table[l2_index];
> -    }
>      if (extent->has_zero_grain && cluster_sector == VMDK_GTE_ZEROED) {
>          zeroed = true;
>      }
> @@ -1231,6 +1224,13 @@ static int get_cluster_offset(BlockDriverState *bs,
>          if (ret) {
>              return ret;
>          }
> +        if (m_data) {
> +            m_data->valid = 1;
> +            m_data->l1_index = l1_index;
> +            m_data->l2_index = l2_index;
> +            m_data->l2_offset = l2_offset;
> +            m_data->l2_cache_entry = &l2_table[l2_index];
> +        }
>      }
>      *cluster_offset = cluster_sector << BDRV_SECTOR_BITS;
>      return VMDK_OK;
> -- 
> 2.9.0
> 

Looks good, nice catch!

Reviewed-by: Fam Zheng <famz@redhat.com>

  reply	other threads:[~2016-07-07  8:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07  8:42 [Qemu-devel] [PATCH v2] vmdk: fix metadata write regression Reda Sallahi
2016-07-07  8:54 ` Fam Zheng [this message]
2016-07-08 13:26 ` Max Reitz

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=20160707085438.GB12042@ad.usersys.redhat.com \
    --to=famz@redhat.com \
    --cc=fullmanet@gmail.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).