qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jun Li <junmuzi@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kwolf@redhat.com, juli@redhat.com, famz@redhat.com,
	qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] qcow2: add update refcount table realization for update_refcount
Date: Sat, 13 Sep 2014 23:53:58 +0800	[thread overview]
Message-ID: <20140913155331.GA22493@localhost.localdomain> (raw)
In-Reply-To: <20140905153343.GH27649@stefanha-thinkpad.redhat.com>

On Fri, 09/05 16:33, Stefan Hajnoczi wrote:
> On Mon, Sep 01, 2014 at 06:52:48PM +0800, Jun Li wrote:
> 
> How does this patch handle self-describing refcount blocks?  I think
> they will keep the refcount block alive forever because your code will
> not decide to free them.
> 

Sorry, I have ignored self-describing refcount blocks. :)

> This patch should also discard the refcount block if we decide to free
> it (in the same way that we discard at cluster_offset).
> 
> > diff --git a/block/qcow2-refcount.c b/block/qcow2-refcount.c
> > index 43665b8..63f36e6 100644
> > --- a/block/qcow2-refcount.c
> > +++ b/block/qcow2-refcount.c
> > @@ -586,6 +586,37 @@ static int QEMU_WARN_UNUSED_RESULT update_refcount(BlockDriverState *bs,
> >          if (refcount == 0 && s->discard_passthrough[type]) {
> >              update_refcount_discard(bs, cluster_offset, s->cluster_size);
> >          }
> > +
> > +        /* When refcount block is NULL, update refcount table */
> > +        if (block_index == 0) {
> 
> What is the purpose of block_index == 0?

Here is want to reduce the probability of running the following code. Only
when block_index == 0, we will run the following code to free refcount block.

> 
> > +            int k = block_index;
> > +            int refcount_block_entries = s->cluster_size / sizeof(uint16_t);
> > +            for (k = 0; k < refcount_block_entries; k++) {
> > +                if (refcount_block[k] != cpu_to_be16(0)) {
> > +                    break;
> > +                }
> > +            }
> > +
> > +            if (k == refcount_block_entries) {
> > +                qemu_vfree(refcount_block);
> 
> You can't do this, the buffer belongs to the refcount block cache.
> Please look at the cache get/put as well as qcow2_cache_create/destroy.

ok, thx. Should add 
qcow2_cache_put(bs, s->refcount_block_cache, (void**) refcount_block);

> 
> > +                /* update refcount table */
> > +                unsigned int refcount_table_index;
> > +                uint64_t data64 = cpu_to_be64(0);
> > +                refcount_table_index = cluster_index >> (s->cluster_bits -
> > +                                       REFCOUNT_SHIFT);
> > +                ret = bdrv_pwrite_sync(bs->file,
> > +                                       s->refcount_table_offset +
> > +                                       refcount_table_index *
> > +                                       sizeof(uint64_t),
> > +                                       &data64, sizeof(data64));
> > +                if (ret < 0) {
> > +                    goto fail;
> > +                }
> 
> Plase use write_reftable_entry().

ok, got it. I will submit a new version when I submit v3 of qcow2 shrinking.


Best Regards,
Jun Li

  reply	other threads:[~2014-09-13 15:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-01 10:52 [Qemu-devel] [PATCH v2] qcow2: add update refcount table realization for update_refcount Jun Li
2014-09-01 11:11 ` Benoît Canet
2014-09-01 16:04   ` Jun Li
2014-09-02 13:38     ` Benoît Canet
2014-09-02 17:12 ` Greg Kurz
2014-09-22  1:45   ` jun muzi
2014-09-05 10:21 ` Kevin Wolf
2014-09-09  2:52   ` Jun Li
2014-09-09  8:21     ` Kevin Wolf
2014-09-09 14:04       ` Jun Li
2014-09-05 15:33 ` Stefan Hajnoczi
2014-09-13 15:53   ` Jun Li [this message]
2014-09-15  9:27     ` Stefan Hajnoczi
2014-09-05 15:34 ` Stefan Hajnoczi

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=20140913155331.GA22493@localhost.localdomain \
    --to=junmuzi@gmail.com \
    --cc=famz@redhat.com \
    --cc=juli@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).