From: Eric Blake <eblake@redhat.com>
To: Denis Plotnikov <dplotnikov@virtuozzo.com>,
armbru@redhat.com, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com, den@virtuozzo.com,
qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 1/3] qcow2: introduce compression type feature
Date: Wed, 4 Sep 2019 10:42:28 -0500 [thread overview]
Message-ID: <fdc02079-9e79-7e23-bf80-b358fb9e6764@redhat.com> (raw)
In-Reply-To: <20190904152915.30755-2-dplotnikov@virtuozzo.com>
[-- Attachment #1.1: Type: text/plain, Size: 2040 bytes --]
On 9/4/19 10:29 AM, Denis Plotnikov wrote:
> The patch adds some preparation parts for incompatible compression type
> feature to QCOW2 header that indicates that *all* compressed clusters
> must be (de)compressed using a certain compression type.
>
> It is implied that the compression type is set on the image creation and
> can be changed only later by image conversion, thus compression type
> defines the only compression algorithm used for the image.
>
> The goal of the feature is to add support of other compression algorithms
> to qcow2. For example, ZSTD which is more effective on compression than ZLIB.
> It works roughly 2x faster than ZLIB providing a comparable compression ratio
> and therefore provides a performance advantage in backup scenarios.
>
> The default compression is ZLIB. Images created with ZLIB compression type
> are backward compatible with older qemu versions.
>
> Signed-off-by: Denis Plotnikov <dplotnikov@virtuozzo.com>
> ---
> +++ b/docs/interop/qcow2.txt
> @@ -165,6 +170,18 @@ in the description of a field.
> Length of the header structure in bytes. For version 2
> images, the length is always assumed to be 72 bytes.
>
> + 104 - 107: compression_type
> + Defines the compression method used for compressed clusters.
> + A single compression type is applied to all compressed image
> + clusters.
> + The compression type is set on image creation only.
This sentence adds nothing for me; you could delete it, and the spec
would still be just as useful (and less questionable about whether I can
'qemu-img amend' an image to use a different compression type in-place
by rewriting all existing compressed clusters).
With or without that sentence,
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-09-04 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 15:29 [Qemu-devel] [PATCH v5 0/3] qcow2: add zstd cluster compression Denis Plotnikov
2019-09-04 15:29 ` [Qemu-devel] [PATCH v5 1/3] qcow2: introduce compression type feature Denis Plotnikov
2019-09-04 15:42 ` Eric Blake [this message]
2019-09-04 15:29 ` [Qemu-devel] [PATCH v5 2/3] qcow2: rework the cluster compression routine Denis Plotnikov
2019-09-04 15:46 ` Eric Blake
2019-09-04 15:46 ` Eric Blake
2019-09-04 15:29 ` [Qemu-devel] [PATCH v5 3/3] qcow2: add zstd cluster compression Denis Plotnikov
2019-09-04 16:07 ` Eric Blake
2019-09-05 7:44 ` Denis Plotnikov
2019-09-05 14:31 ` Eric Blake
2019-09-05 14:52 ` Denis Plotnikov
2019-09-05 8:52 ` Denis Plotnikov
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=fdc02079-9e79-7e23-bf80-b358fb9e6764@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=den@virtuozzo.com \
--cc=dplotnikov@virtuozzo.com \
--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).