From: Eric Blake <eblake@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org
Cc: "Denis V. Lunev" <den@openvz.org>,
anton.nefedov@virtuozzo.com, qemu-devel@nongnu.org,
mreitz@redhat.com
Subject: Re: [PATCH] qcow2: Reduce write_zeroes size in handle_alloc_space()
Date: Tue, 9 Jun 2020 09:46:24 -0500 [thread overview]
Message-ID: <042f0b8f-dd51-acc3-8498-ac9a5532df15@redhat.com> (raw)
In-Reply-To: <02e24dca-99da-873d-8425-09a07571e675@virtuozzo.com>
On 6/9/20 9:28 AM, Vladimir Sementsov-Ogievskiy wrote:
> 09.06.2020 17:08, Kevin Wolf wrote:
>> Since commit c8bb23cbdbe, handle_alloc_space() is called for newly
>> allocated clusters to efficiently initialise the COW areas with zeros if
>> necessary. It skips the whole operation if both start_cow nor end_cow
>> are empty. However, it requests zeroing the whole request size (possibly
>> multiple megabytes) even if only one end of the request actually needs
>> this.
>>
>> This patch reduces the write_zeroes request size in this case so that we
>> don't unnecessarily zero-initialise a region that we're going to
>> overwrite immediately.
>>
>
> Hmm, I'm afraid, that this may make things worse in some cases, as with
> one big write-zero request
> we preallocate data-region in the protocol file, so we have better
> locality for the clusters we
> are going to write. And, in the same time, with BDRV_REQ_NO_FALLBACK
> flag write-zero must be
> fast anyway (especially in comparison with the following write request).
>
>> /*
>> * instead of writing zero COW buffers,
>> * efficiently zero out the whole clusters
>> */
>> - ret = qcow2_pre_write_overlap_check(bs, 0, m->alloc_offset,
>> - m->nb_clusters *
>> s->cluster_size,
>> - true);
>> + ret = qcow2_pre_write_overlap_check(bs, 0, start, len, true);
>> if (ret < 0) {
>> return ret;
>> }
>> BLKDBG_EVENT(bs->file, BLKDBG_CLUSTER_ALLOC_SPACE);
>> - ret = bdrv_co_pwrite_zeroes(s->data_file, m->alloc_offset,
>> - m->nb_clusters * s->cluster_size,
>> + ret = bdrv_co_pwrite_zeroes(s->data_file, start, len,
>> BDRV_REQ_NO_FALLBACK);
Good point. If we weren't using BDRV_REQ_NO_FALLBACK, then avoiding a
pre-zero pass over the middle is essential. But since we are insisting
that the pre-zero pass be fast or else immediately fail, the time spent
in pre-zeroing should not be a concern. Do you have benchmark numbers
stating otherwise?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-06-09 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 14:08 [PATCH] qcow2: Reduce write_zeroes size in handle_alloc_space() Kevin Wolf
2020-06-09 14:28 ` Vladimir Sementsov-Ogievskiy
2020-06-09 14:46 ` Eric Blake [this message]
2020-06-09 15:18 ` Kevin Wolf
2020-06-09 15:29 ` Vladimir Sementsov-Ogievskiy
2020-06-10 8:38 ` Vladimir Sementsov-Ogievskiy
2020-06-09 16:19 ` Eric Blake
2020-06-10 6:50 ` Vladimir Sementsov-Ogievskiy
2020-06-10 11:25 ` Kevin Wolf
2020-06-09 14:43 ` Eric Blake
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=042f0b8f-dd51-acc3-8498-ac9a5532df15@redhat.com \
--to=eblake@redhat.com \
--cc=anton.nefedov@virtuozzo.com \
--cc=den@openvz.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).