From: Eric Blake <eblake@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org
Cc: kwolf@redhat.com, armbru@redhat.com, qemu-devel@nongnu.org,
dplotnikov@virtuozzo.com, den@openvz.org, mreitz@redhat.com
Subject: Re: [PATCH v11 2/2] docs: qcow2: introduce compression type feature
Date: Fri, 31 Jan 2020 08:46:12 -0600 [thread overview]
Message-ID: <ee6b018a-be33-ed77-c4b9-4894c685d30a@redhat.com> (raw)
In-Reply-To: <20200131142219.3264-3-vsementsov@virtuozzo.com>
On 1/31/20 8:22 AM, Vladimir Sementsov-Ogievskiy wrote:
> The patch adds a new additional field to the qcow2 header: compression_type,
> which specifies compression type. If field is absent or zero, default
> compression type is set: ZLIB, which corresponds to current behavior.
>
> New compression type (ZSTD) is to be added in further commit.
>
> Suggested-by: Denis Plotnikov <dplotnikov@virtuozzo.com>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
> docs/interop/qcow2.txt | 19 ++++++++++++++++++-
> 1 file changed, 18 insertions(+), 1 deletion(-)
>
> diff --git a/docs/interop/qcow2.txt b/docs/interop/qcow2.txt
> index 823cc266e0..3a8d5c0c6e 100644
> --- a/docs/interop/qcow2.txt
> +++ b/docs/interop/qcow2.txt
> @@ -109,6 +109,11 @@ the next fields through header_length.
> An External Data File Name header extension may
> be present if this bit is set.
>
> + Bit 3: Compression type bit. If this bit is set,
> + a non-default compression is used for compressed
> + clusters. The compression_type field must be
> + present and not zero.
> +
I'm still not sold on this. What's wrong with:
Bit 3: Compression type bit. If this bit is set,
a non-default compression may be used for
compressed clusters, and the compression_type
field must be present.
> Bits 3-63: Reserved (set to 0)
>
> 80 - 87: compatible_features
> @@ -190,7 +195,19 @@ present*, if not altered by a specific incompatible bit.
> to the field's offset. Also, all additional fields are not present for
> version 2.
>
> - < ... No additional fields in the header currently ... >
> + 104: compression_type
> +
> + Defines the compression method used for compressed clusters.
> + All compressed clusters in an image use the same compression
> + type.
> +
> + If the incompatible bit "Compression type" is set: the field
> + must be present and non-zero (which means non-zlib
> + compression type). Otherwise, this field must not be present
> + or must be zero (which means zlib).
If the incompatible bit "Compression type" is set: the field
must be present. Otherwise, this field must not be present
or must be zero (which means zlib). It is recommended but
not required that the "Compression type" bit be clear if this
field is present but zero.
> +
> + Available compression type values:
> + 0: zlib <https://www.zlib.net/>
>
>
> === Header padding ===
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-01-31 14:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 14:22 [PATCH v11 0/2] docs: qcow2: introduce compression type feature Vladimir Sementsov-Ogievskiy
2020-01-31 14:22 ` [PATCH v11 1/2] docs: improve qcow2 spec about extending image header Vladimir Sementsov-Ogievskiy
2020-01-31 14:46 ` Eric Blake
2020-01-31 17:13 ` Alberto Garcia
2020-01-31 14:22 ` [PATCH v11 2/2] docs: qcow2: introduce compression type feature Vladimir Sementsov-Ogievskiy
2020-01-31 14:46 ` Eric Blake [this message]
2020-01-31 17:34 ` Alberto Garcia
2020-01-31 17:49 ` Eric Blake
2020-01-31 18:15 ` Vladimir Sementsov-Ogievskiy
2020-01-31 22:14 ` Alberto Garcia
2020-02-06 12:38 ` Max Reitz
2020-02-06 14:08 ` Eric Blake
2020-02-06 13:51 ` [PATCH v11 0/2] " Max Reitz
2020-02-06 14:30 ` Vladimir Sementsov-Ogievskiy
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=ee6b018a-be33-ed77-c4b9-4894c685d30a@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--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).