From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] qcow2: Set zero flag for discarded clusters
Date: Fri, 14 Feb 2014 19:11:30 +0100 [thread overview]
Message-ID: <20140214181130.GL32343@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <20140214170512.GA7660@stefanha-thinkpad.redhat.com>
Am 14.02.2014 um 18:05 hat Stefan Hajnoczi geschrieben:
> On Sat, Feb 08, 2014 at 05:50:02PM +0100, Kevin Wolf wrote:
> > Instead of making the backing file contents visible again after a discard
> > request, set the zero flag if possible (i.e. on version >= 3).
> >
> > Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> > Reviewed-by: Max Reitz <mreitz@redhat.com>
> > ---
> > block/qcow2-cluster.c | 22 ++++++++++++++++++++--
> > 1 file changed, 20 insertions(+), 2 deletions(-)
> >
> > diff --git a/block/qcow2-cluster.c b/block/qcow2-cluster.c
> > index 25d45d1..9461969 100644
> > --- a/block/qcow2-cluster.c
> > +++ b/block/qcow2-cluster.c
> > @@ -1333,13 +1333,31 @@ static int discard_single_l2(BlockDriverState *bs, uint64_t offset,
> > uint64_t old_offset;
> >
> > old_offset = be64_to_cpu(l2_table[l2_index + i]);
> > - if ((old_offset & L2E_OFFSET_MASK) == 0) {
> > +
> > + /*
> > + * Make sure that a discarded area reads back as zeroes for v3 images
> > + * (we cannot do it for v2 without actually writing a zero-filled
> > + * buffer). We can skip the operation if the cluster is already marked
> > + * as zero, or if it's unallocated and we don't have a backing file.
> > + *
> > + * TODO We might want to use bdrv_get_block_status(bs) here, but we're
> > + * holding s->lock, so that doesn't work today.
> > + */
> > + if (!!(old_offset & QCOW_OFLAG_ZERO)) {
> > + continue;
> > + }
> > +
> > + if ((old_offset & L2E_OFFSET_MASK) == 0 && !bs->backing_hd) {
> > continue;
> > }
> >
> > /* First remove L2 entries */
> > qcow2_cache_entry_mark_dirty(s->l2_table_cache, l2_table);
> > - l2_table[l2_index + i] = cpu_to_be64(0);
> > + if (s->qcow_version >= 3) {
> > + l2_table[l2_index + i] = cpu_to_be64(QCOW_OFLAG_ZERO);
> > + } else {
> > + l2_table[l2_index + i] = cpu_to_be64(0);
> > + }
> >
> > /* Then decrease the refcount */
> > qcow2_free_any_clusters(bs, old_offset, 1, type);
>
> Oops, this breaks qemu-iotests 046. I have dropped it from the pull request.
Okay. This is kind of nasty, because we now have different expected
results for v2 and v3 images. I'll have to see how the test case is
fixed in the best way. Perhaps it's best not to check discarded areas at
all, because strictly speaking they are undefined.
Kevin
next prev parent reply other threads:[~2014-02-14 18:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 15:28 [Qemu-devel] [PATCH] qcow2: Set zero flag for discarded clusters Kevin Wolf
2014-02-08 16:11 ` Max Reitz
2014-02-08 16:17 ` Max Reitz
2014-02-08 16:32 ` Kevin Wolf
2014-02-08 16:50 ` [Qemu-devel] [PATCH v2] " Kevin Wolf
2014-02-14 14:34 ` Stefan Hajnoczi
2014-02-14 17:05 ` Stefan Hajnoczi
2014-02-14 18:11 ` Kevin Wolf [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-17 14:45 Kevin Wolf
2014-02-17 17:12 ` Eric Blake
2014-02-18 11:29 ` Kevin Wolf
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=20140214181130.GL32343@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@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).