From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Anton Nefedov <anton.nefedov@virtuozzo.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "qemu-block@nongnu.org" <qemu-block@nongnu.org>,
"kwolf@redhat.com" <kwolf@redhat.com>,
"mreitz@redhat.com" <mreitz@redhat.com>,
"eblake@redhat.com" <eblake@redhat.com>,
Denis Lunev <den@virtuozzo.com>,
"berto@igalia.com" <berto@igalia.com>
Subject: Re: [Qemu-devel] [PATCH v10 8/9] qcow2: skip writing zero buffers to empty COW areas
Date: Wed, 5 Dec 2018 17:42:06 +0000 [thread overview]
Message-ID: <743b0aed-10e3-d26b-b13f-81025811fef2@virtuozzo.com> (raw)
In-Reply-To: <70c2fceb-a0ae-f6a1-7f20-a4339ce37237@virtuozzo.com>
05.12.2018 19:59, Anton Nefedov wrote:
> On 5/12/2018 5:01 PM, Vladimir Sementsov-Ogievskiy wrote:
>> 03.12.2018 13:14, Anton Nefedov wrote:
>>> If COW areas of the newly allocated clusters are zeroes on the backing image,
>>> efficient bdrv_write_zeroes(flags=BDRV_REQ_ALLOCATE) can be used on the whole
>>> cluster instead of writing explicit zero buffers later in perform_cow().
>>>
>>> iotest 060:
>>> write to the discarded cluster does not trigger COW anymore.
>>> Use a backing image instead.
>>>
>>> Signed-off-by: Anton Nefedov <anton.nefedov@virtuozzo.com>
>>> Reviewed-by: Alberto Garcia <berto@igalia.com>
>>> ---
>>> qapi/block-core.json | 4 +-
>>> block/qcow2.h | 6 +++
>>> block/qcow2-cluster.c | 2 +-
>>> block/qcow2.c | 80 +++++++++++++++++++++++++++++++++++++-
>>> block/trace-events | 1 +
>>> tests/qemu-iotests/060 | 26 ++++++++-----
>>> tests/qemu-iotests/060.out | 5 ++-
>>> 7 files changed, 109 insertions(+), 15 deletions(-)
>>>
>>> diff --git a/qapi/block-core.json b/qapi/block-core.json
>>> index d4fe710836..50598aa8fe 100644
>>> --- a/qapi/block-core.json
>>> +++ b/qapi/block-core.json
>>> @@ -3004,6 +3004,8 @@
>>> #
>>> # @cor_write: a write due to copy-on-read (since 2.11)
>>> #
>>> +# @cluster_alloc_space: an allocation of file space for a cluster (since 4.0)
>>> +#
>>> # Since: 2.9
>>> ##
>>> { 'enum': 'BlkdebugEvent', 'prefix': 'BLKDBG',
>>> @@ -3022,7 +3024,7 @@
>>> 'pwritev_rmw_tail', 'pwritev_rmw_after_tail', 'pwritev',
>>> 'pwritev_zero', 'pwritev_done', 'empty_image_prepare',
>>> 'l1_shrink_write_table', 'l1_shrink_free_l2_clusters',
>>> - 'cor_write'] }
>>> + 'cor_write', 'cluster_alloc_space'] }
>>>
>>> ##
>>> # @BlkdebugInjectErrorOptions:
>>> diff --git a/block/qcow2.h b/block/qcow2.h
>>> index 8662b68575..8a64077897 100644
>>> --- a/block/qcow2.h
>>> +++ b/block/qcow2.h
>>> @@ -389,6 +389,12 @@ typedef struct QCowL2Meta
>>> */
>>> Qcow2COWRegion cow_end;
>>>
>>> + /**
>>> + * Indicates that COW regions are already handled and do not require
>>> + * any more processing.
>>> + */
>>> + bool skip_cow;
>>> +
>>> /**
>>> * The I/O vector with the data from the actual guest write request.
>>> * If non-NULL, this is meant to be merged together with the data
>>> diff --git a/block/qcow2-cluster.c b/block/qcow2-cluster.c
>>> index d37fe08b3d..3685c5f67e 100644
>>> --- a/block/qcow2-cluster.c
>>> +++ b/block/qcow2-cluster.c
>>> @@ -806,7 +806,7 @@ static int perform_cow(BlockDriverState *bs, QCowL2Meta *m)
>>> assert(start->offset + start->nb_bytes <= end->offset);
>>> assert(!m->data_qiov || m->data_qiov->size == data_bytes);
>>>
>>> - if (start->nb_bytes == 0 && end->nb_bytes == 0) {
>>> + if ((start->nb_bytes == 0 && end->nb_bytes == 0) || m->skip_cow) {
>>> return 0;
>>> }
>>>
>>> diff --git a/block/qcow2.c b/block/qcow2.c
>>> index 991d6ac91b..027188a1a3 100644
>>> --- a/block/qcow2.c
>>> +++ b/block/qcow2.c
>>> @@ -2015,6 +2015,11 @@ static bool merge_cow(uint64_t offset, unsigned bytes,
>>> continue;
>>> }
>>>
>>> + /* If COW regions are handled already, skip this too */
>>> + if (m->skip_cow) {
>>> + continue;
>>> + }
>>> +
>>> /* The data (middle) region must be immediately after the
>>> * start region */
>>> if (l2meta_cow_start(m) + m->cow_start.nb_bytes != offset) {
>>> @@ -2040,6 +2045,68 @@ static bool merge_cow(uint64_t offset, unsigned bytes,
>>> return false;
>>> }
>>>
>>> +static bool is_unallocated(BlockDriverState *bs, int64_t offset, int64_t bytes)
>>> +{
>>> + int64_t nr;
>>> + return !bytes ||
>>> + (!bdrv_is_allocated_above(bs, NULL, offset, bytes, &nr) && nr == bytes);
>>
>> bdrv_is_allocated_above may return error < 0
>>
>
> Probably I just took is_zero() as an example.
> But somewhere there's even a rationale (bdrv_co_do_copy_on_readv):
>
> ret = bdrv_is_allocated(bs, cluster_offset,
> MIN(cluster_bytes, max_transfer), &pnum);
> if (ret < 0) {
> /* Safe to treat errors in querying allocation as if
> * unallocated; we'll probably fail again soon on the
> * read, but at least that will set a decent errno.
> */
> pnum = MIN(cluster_bytes, max_transfer);
> }
aha, anyway, !bdrv_is_allocated_above is true when and only when the function
successfully returned "unallocated".
ahaha, this rationale has funny mistake: s/unallocated/allocated )
--
Best regards,
Vladimir
next prev parent reply other threads:[~2018-12-05 17:42 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 10:14 [Qemu-devel] [PATCH v10 0/9] qcow2: cluster space preallocation Anton Nefedov
2018-12-03 10:14 ` [Qemu-devel] [PATCH v10 1/9] mirror: inherit supported write/zero flags Anton Nefedov
2018-12-05 12:43 ` Vladimir Sementsov-Ogievskiy
2018-12-05 13:27 ` Anton Nefedov
2018-12-07 14:31 ` Alberto Garcia
2018-12-12 12:15 ` Vladimir Sementsov-Ogievskiy
2018-12-03 10:14 ` [Qemu-devel] [PATCH v10 2/9] blkverify: set " Anton Nefedov
2018-12-07 14:32 ` Alberto Garcia
2018-12-12 12:26 ` Vladimir Sementsov-Ogievskiy
2018-12-03 10:14 ` [Qemu-devel] [PATCH v10 3/9] quorum: set supported write flags Anton Nefedov
2018-12-07 14:33 ` Alberto Garcia
2018-12-07 14:46 ` Anton Nefedov
2018-12-07 14:54 ` Alberto Garcia
2018-12-12 12:33 ` Vladimir Sementsov-Ogievskiy
2018-12-03 10:14 ` [Qemu-devel] [PATCH v10 4/9] block: introduce BDRV_REQ_ALLOCATE flag Anton Nefedov
2018-12-05 12:59 ` Vladimir Sementsov-Ogievskiy
2018-12-05 13:38 ` Anton Nefedov
2018-12-03 10:14 ` [Qemu-devel] [PATCH v10 5/9] block: treat BDRV_REQ_ALLOCATE as serialising Anton Nefedov
2018-12-05 13:14 ` Vladimir Sementsov-Ogievskiy
2018-12-05 14:01 ` Anton Nefedov
2018-12-12 12:48 ` Vladimir Sementsov-Ogievskiy
2018-12-13 11:57 ` Anton Nefedov
2018-12-03 10:14 ` [Qemu-devel] [PATCH v10 6/9] file-posix: support BDRV_REQ_ALLOCATE Anton Nefedov
2018-12-05 13:25 ` Vladimir Sementsov-Ogievskiy
2018-12-05 14:11 ` Anton Nefedov
2018-12-12 17:19 ` Vladimir Sementsov-Ogievskiy
2018-12-13 12:01 ` Anton Nefedov
2018-12-07 15:09 ` Alberto Garcia
2018-12-03 10:14 ` [Qemu-devel] [PATCH v10 8/9] qcow2: skip writing zero buffers to empty COW areas Anton Nefedov
2018-12-03 13:59 ` Alberto Garcia
2018-12-03 14:04 ` Anton Nefedov
2018-12-05 14:01 ` Vladimir Sementsov-Ogievskiy
2018-12-05 16:59 ` Anton Nefedov
2018-12-05 17:42 ` Vladimir Sementsov-Ogievskiy [this message]
2018-12-13 12:02 ` Vladimir Sementsov-Ogievskiy
2018-12-13 13:57 ` Anton Nefedov
2018-12-14 16:20 ` Vladimir Sementsov-Ogievskiy
2018-12-17 10:17 ` Anton Nefedov
2018-12-03 10:14 ` [Qemu-devel] [PATCH v10 7/9] block: support BDRV_REQ_ALLOCATE in passthrough drivers Anton Nefedov
2018-12-05 13:28 ` Vladimir Sementsov-Ogievskiy
2018-12-07 15:00 ` Alberto Garcia
2018-12-03 10:15 ` [Qemu-devel] [PATCH v10 9/9] iotest 134: test cluster-misaligned encrypted write Anton Nefedov
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=743b0aed-10e3-d26b-b13f-81025811fef2@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=anton.nefedov@virtuozzo.com \
--cc=berto@igalia.com \
--cc=den@virtuozzo.com \
--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 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).