From: Max Reitz <mreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>,
Anton Nefedov <anton.nefedov@virtuozzo.com>,
qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, kwolf@redhat.com, den@virtuozzo.com,
berto@igalia.com
Subject: Re: [Qemu-devel] [PATCH v7 8/9] qcow2: skip writing zero buffers to empty COW areas
Date: Wed, 31 Jan 2018 19:35:17 +0100 [thread overview]
Message-ID: <7b4ac9d9-1e51-43d4-0d55-488ac5593263@redhat.com> (raw)
In-Reply-To: <cfcdb124-b343-ae2f-726d-5b084c9b86bb@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1947 bytes --]
On 2018-01-31 19:32, Eric Blake wrote:
> On 01/31/2018 11:40 AM, Max Reitz wrote:
>
>>> Maybe it's good enough to cover these cases:
>>> 1. no backing
>>> 2. beyond bdrv_getlength() in backing
>>> 3. unallocated in backing qcow2 (covers 'beyond bdrv_getlength()
>>> in backing->file')
>>>
>>> 1 & 2 are easy to check;
>>
>> Not sure how useful 2 is, though. (I don't know. I always hear about
>> people wanting to optimize for such a case where a backing file is
>> shorter than the overlay, but I can't imagine a real use case for that.)
>
> I can; here's what's happened to me personally. I created an image, and
> took internal snapshots (yeah, I know those aren't in fashion these
> days, but this was long ago). Later, I ran out of space. I wanted to
> resize the image, but am not convinced whether resizing the image will
> play nicely with the internal snapshots (in fact, I don't recall
> off-hand whether this was something we prevented in the past and now
> support, or if it is still unsupported now...) - so the easiest way is
> to create a larger overlay image.
But you were convinced that creating an overlay would play nicely with
the internal snapshots? ;-)
I'm not sure whether that sounds like a use case I'd want to optimize
for, but, well.
>>> 3: if that's not too hacky maybe we can do the bdrv_is_allocated() check
>>> for qcow2 exclusively and if there is raw (or any other format) backing
>>> image - do the COW
>>
>> Yes, well, it seems useful in principle... But it would require general
>> block layer work indeed. Maybe a new flag for bdrv_block_status*() that
>> says only to look into the format layer?
>
> Maybe indeed - but first I want my byte-based block_status stuff to land ;)
It could be done as an optimization in a follow-up to this series
anyway, yes.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2018-01-31 18:35 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 17:48 [Qemu-devel] [PATCH v7 0/9] qcow2: cluster space preallocation Anton Nefedov
2018-01-18 17:48 ` [Qemu-devel] [PATCH v7 1/9] mirror: inherit supported write/zero flags Anton Nefedov
2018-01-29 19:21 ` Max Reitz
2018-01-29 19:26 ` Eric Blake
2018-01-30 12:15 ` Anton Nefedov
2018-01-30 16:00 ` Eric Blake
2018-01-31 17:20 ` Max Reitz
2018-01-18 17:49 ` [Qemu-devel] [PATCH v7 2/9] blkverify: set " Anton Nefedov
2018-01-29 19:23 ` Max Reitz
2018-01-18 17:49 ` [Qemu-devel] [PATCH v7 3/9] block: introduce BDRV_REQ_ALLOCATE flag Anton Nefedov
2018-01-29 19:37 ` Max Reitz
2018-01-30 12:34 ` Anton Nefedov
2018-01-31 17:31 ` Max Reitz
2018-02-01 13:34 ` Anton Nefedov
2018-02-01 18:06 ` Max Reitz
2018-01-18 17:49 ` [Qemu-devel] [PATCH v7 4/9] block: treat BDRV_REQ_ALLOCATE as serialising Anton Nefedov
2018-01-29 19:48 ` Max Reitz
2018-01-30 12:36 ` Anton Nefedov
2018-01-31 17:35 ` Max Reitz
2018-01-31 15:11 ` Alberto Garcia
2018-01-31 17:11 ` Anton Nefedov
2018-02-01 14:01 ` Alberto Garcia
2018-01-18 17:49 ` [Qemu-devel] [PATCH v7 5/9] file-posix: support BDRV_REQ_ALLOCATE Anton Nefedov
2018-01-29 19:56 ` Max Reitz
2018-01-18 17:49 ` [Qemu-devel] [PATCH v7 6/9] block: support BDRV_REQ_ALLOCATE in passthrough drivers Anton Nefedov
2018-01-29 19:58 ` Max Reitz
2018-01-18 17:49 ` [Qemu-devel] [PATCH v7 7/9] qcow2: move is_zero() up Anton Nefedov
2018-01-29 19:59 ` Max Reitz
2018-01-18 17:49 ` [Qemu-devel] [PATCH v7 8/9] qcow2: skip writing zero buffers to empty COW areas Anton Nefedov
2018-01-29 20:28 ` Max Reitz
2018-01-30 14:23 ` Anton Nefedov
2018-01-31 17:40 ` Max Reitz
2018-01-31 18:32 ` Eric Blake
2018-01-31 18:35 ` Max Reitz [this message]
2018-01-31 18:43 ` Eric Blake
2018-01-18 17:49 ` [Qemu-devel] [PATCH v7 9/9] iotest 134: test cluster-misaligned encrypted write Anton Nefedov
2018-01-29 20:30 ` Max Reitz
2018-01-30 13:03 ` Alberto Garcia
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=7b4ac9d9-1e51-43d4-0d55-488ac5593263@redhat.com \
--to=mreitz@redhat.com \
--cc=anton.nefedov@virtuozzo.com \
--cc=berto@igalia.com \
--cc=den@virtuozzo.com \
--cc=eblake@redhat.com \
--cc=kwolf@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).