From: "Denis V. Lunev" <den@openvz.org>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, kwolf@redhat.com, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 5/5] qcow2: Catch more unaligned write_zero into zero cluster
Date: Thu, 26 May 2016 16:41:16 +0300 [thread overview]
Message-ID: <5746FCFC.2060708@openvz.org> (raw)
In-Reply-To: <1464234529-13018-6-git-send-email-eblake@redhat.com>
On 05/26/2016 06:48 AM, Eric Blake wrote:
> is_zero_cluster() and is_zero_cluster_top_locked() are used only
> by qcow2_co_write_zeroes(). The former is too broad (we don't
> care if the sectors we are about to overwrite are non-zero, only
> that all other sectors in the cluster are zero), so it needs to
> be called up to twice but with smaller limits - rename it along
> with adding the neeeded parameter. The latter can be inlined for
> more compact code.
>
> The testsuite change shows that we now have a sparser top file
> when an unaligned write_zeroes overwrites the only portion of
> the backing file with data.
>
> Based on a patch proposal by Denis V. Lunev.
>
> CC: Denis V. Lunev <den@openvz.org>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
> block/qcow2.c | 47 +++++++++++++++++++++++-----------------------
> tests/qemu-iotests/154.out | 8 ++++----
> 2 files changed, 27 insertions(+), 28 deletions(-)
>
> diff --git a/block/qcow2.c b/block/qcow2.c
> index 105fd5e..ecac399 100644
> --- a/block/qcow2.c
> +++ b/block/qcow2.c
> @@ -2406,26 +2406,19 @@ finish:
> }
>
>
> -static bool is_zero_cluster(BlockDriverState *bs, int64_t start)
> +static bool is_zero_sectors(BlockDriverState *bs, int64_t start,
> + uint32_t count)
> {
> - BDRVQcow2State *s = bs->opaque;
> int nr;
> BlockDriverState *file;
> - int64_t res = bdrv_get_block_status_above(bs, NULL, start,
> - s->cluster_sectors, &nr, &file);
> - return res >= 0 && (res & BDRV_BLOCK_ZERO) && nr == s->cluster_sectors;
> -}
> + int64_t res;
>
> -static bool is_zero_cluster_top_locked(BlockDriverState *bs, int64_t start)
> -{
> - BDRVQcow2State *s = bs->opaque;
> - int nr = s->cluster_sectors;
> - uint64_t off;
> - int ret;
> -
> - ret = qcow2_get_cluster_offset(bs, start << BDRV_SECTOR_BITS, &nr, &off);
> - assert(nr == s->cluster_sectors);
> - return ret == QCOW2_CLUSTER_UNALLOCATED || ret == QCOW2_CLUSTER_ZERO;
> + if (!count) {
> + return true;
> + }
> + res = bdrv_get_block_status_above(bs, NULL, start, count,
> + &nr, &file);
> + return res >= 0 && (res & BDRV_BLOCK_ZERO) && nr == count;
> }
>
> static coroutine_fn int qcow2_co_write_zeroes(BlockDriverState *bs,
> @@ -2434,27 +2427,33 @@ static coroutine_fn int qcow2_co_write_zeroes(BlockDriverState *bs,
> int ret;
> BDRVQcow2State *s = bs->opaque;
>
> - int head = sector_num % s->cluster_sectors;
> - int tail = (sector_num + nb_sectors) % s->cluster_sectors;
> + uint32_t head = sector_num % s->cluster_sectors;
> + uint32_t tail = (sector_num + nb_sectors) % s->cluster_sectors;
>
> trace_qcow2_write_zeroes_start_req(qemu_coroutine_self(), sector_num,
> nb_sectors);
>
> - if (head != 0 || tail != 0) {
> + if (head || tail) {
> int64_t cl_start = sector_num - head;
> + uint64_t off;
> + int nr;
>
> assert(cl_start + s->cluster_sectors >= sector_num + nb_sectors);
>
> - sector_num = cl_start;
> - nb_sectors = s->cluster_sectors;
> -
> - if (!is_zero_cluster(bs, sector_num)) {
> + /* check whether remainder of cluster already reads as zero */
> + if (!(is_zero_sectors(bs, cl_start, head) &&
> + is_zero_sectors(bs, sector_num + nb_sectors,
> + -tail & (s->cluster_sectors - 1)))) {
can we have cluster_sectors != 2^n?
In this case this bits logic will be broken.
next prev parent reply other threads:[~2016-05-26 13:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 3:48 [Qemu-devel] [PATCH v3 0/5] qcow2_co_write_zeroes and related improvements Eric Blake
2016-05-26 3:48 ` [Qemu-devel] [PATCH v3 1/5] block: split write_zeroes always Eric Blake
2016-05-26 8:51 ` Fam Zheng
2016-05-26 3:48 ` [Qemu-devel] [PATCH v3 2/5] qcow2: simplify logic in qcow2_co_write_zeroes Eric Blake
2016-05-26 3:48 ` [Qemu-devel] [PATCH v3 3/5] qcow2: add tracepoints for qcow2_co_write_zeroes Eric Blake
2016-05-26 3:48 ` [Qemu-devel] [PATCH v3 4/5] qemu-iotests: Test one more spot for optimizing write_zeroes Eric Blake
2016-05-26 3:48 ` [Qemu-devel] [PATCH v3 5/5] qcow2: Catch more unaligned write_zero into zero cluster Eric Blake
2016-05-26 13:41 ` Denis V. Lunev [this message]
2016-05-26 14:35 ` Eric Blake
2016-06-02 10:14 ` Kevin Wolf
2016-06-02 12:33 ` Eric Blake
2016-05-26 14:56 ` Denis V. Lunev
2016-06-02 10:20 ` [Qemu-devel] [PATCH v3 0/5] qcow2_co_write_zeroes and related improvements 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=5746FCFC.2060708@openvz.org \
--to=den@openvz.org \
--cc=eblake@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.