From: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
To: Max Reitz <mreitz@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
"fam@euphon.net" <fam@euphon.net>,
Denis Lunev <den@virtuozzo.com>,
"armbru@redhat.com" <armbru@redhat.com>,
"stefanha@redhat.com" <stefanha@redhat.com>
Subject: Re: [PATCH v5 1/4] block: support compressed write at generic layer
Date: Thu, 24 Oct 2019 12:56:44 +0000 [thread overview]
Message-ID: <539e7d9e-0cb7-fdb7-f376-1648361ec2f3@virtuozzo.com> (raw)
In-Reply-To: <4fd89d2a-94aa-6f2d-ed7d-7633356e5163@redhat.com>
On 24/10/2019 12:34, Max Reitz wrote:
> On 22.10.19 15:53, Andrey Shinkevich wrote:
>
> [...]
>
>> If the support of COW for compressed writes is found feasible, will it
>> make a sense to implement? Then this series will follow.
>
> Hm, what exactly do you mean by support of COW for compressed writes?
>
I spoke in terms of the commit message with the following ID:
b0b6862e5e1a1394e0ab3d5da94ba8b0da8664e2
"qcow2: Fail write_compressed when overwriting data"
"...qcow2_write_compressed() doesn't perform COW as it would have to do..."
So, I suggest that we implement writing compressed data to the allocated
clusters rather than qcow2_alloc_compressed_cluster_offset() returns the
error. Particularly, when it comes to NBD server connection failure for
writhing a compressed cluster, it may not be rewritten after the
connection is restored.
Are there any issues with that implementation idea?
Andrey
>> A comment for the option would warn a user that guest writing will work
>> slower for if compress selected.
>
> I’m not sure whether that’s necessary. As a user, I would assume that
> enabling compression will always make something slower.
>
> Max
>
next prev parent reply other threads:[~2019-10-24 13:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 20:37 [PATCH v5 0/4] qcow2: advanced compression options Andrey Shinkevich
2019-10-20 20:37 ` [PATCH v5 1/4] block: support compressed write at generic layer Andrey Shinkevich
2019-10-22 9:28 ` Max Reitz
2019-10-22 10:21 ` Andrey Shinkevich
2019-10-22 10:46 ` Vladimir Sementsov-Ogievskiy
2019-10-22 11:31 ` Max Reitz
2019-10-22 12:23 ` Vladimir Sementsov-Ogievskiy
2019-10-22 12:56 ` Max Reitz
2019-10-22 13:53 ` Andrey Shinkevich
2019-10-24 9:34 ` Max Reitz
2019-10-24 12:56 ` Andrey Shinkevich [this message]
2019-10-24 13:48 ` Max Reitz
2019-10-24 14:07 ` Andrey Shinkevich
2019-10-24 15:12 ` Max Reitz
2019-10-24 14:27 ` Andrey Shinkevich
2019-10-22 14:28 ` Vladimir Sementsov-Ogievskiy
2019-10-20 20:37 ` [PATCH v5 2/4] qcow2: Allow writing compressed data of multiple clusters Andrey Shinkevich
2019-10-20 20:37 ` [PATCH v5 3/4] tests/qemu-iotests: add case to write " Andrey Shinkevich
2019-10-20 20:37 ` [PATCH v5 4/4] tests/qemu-iotests: add case for block-stream compress Andrey Shinkevich
2019-10-22 9:28 ` Max Reitz
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=539e7d9e-0cb7-fdb7-f376-1648361ec2f3@virtuozzo.com \
--to=andrey.shinkevich@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@virtuozzo.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--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).