From: Markus Armbruster <armbru@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
Denis Plotnikov <dplotnikov@virtuozzo.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: ImageInfo oddities regarding compression
Date: Fri, 27 Nov 2020 11:06:36 +0100 [thread overview]
Message-ID: <87r1ofru4z.fsf@dusky.pond.sub.org> (raw)
ImageInfo has an optional member @compressed:
##
# @ImageInfo:
[...]
# @compressed: true if the image is compressed (Since 1.7)
Doc bug: neglects to specify the default. I guess it's false.
The only user appears to be vmdk_get_extent_info(). Goes back to
v1.7.0's commits
f4c129a38a vmdk: Implment bdrv_get_specific_info
cbe82d7fb3 qapi: Add optional field 'compressed' to ImageInfo
ImageInfo also has an optional member @format-specific.
Doc bug: neglects to specify when it's present. I assume it's always
present when member @format has a value that has a non-empty variant in
@format-specific's type ImageInfoSpecific.
Format qcow2's variant is ImageInfoSpecificQCow2. It has a mandatory
member @compression-type.
##
# @Qcow2CompressionType:
#
# Compression type used in qcow2 image file
#
# @zlib: zlib compression, see <http://zlib.net/>
# @zstd: zstd compression, see <http://github.com/facebook/zstd>
#
# Since: 5.1
##
{ 'enum': 'Qcow2CompressionType',
'data': [ 'zlib', { 'name': 'zstd', 'if': 'defined(CONFIG_ZSTD)' } ] }
Apparently, you can't have a qcow2 image without compression. Correct?
Can you imagine a use case for "without compression"?
I fell down this (thankfully shallow) rabbit hole because we also have
{ 'enum': 'MultiFDCompression',
'data': [ 'none', 'zlib',
{ 'name': 'zstd', 'if': 'defined(CONFIG_ZSTD)' } ] }
I wonder whether we could merge them into a common type.
next reply other threads:[~2020-11-27 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 10:06 Markus Armbruster [this message]
2020-11-27 10:14 ` ImageInfo oddities regarding compression Daniel P. Berrangé
2020-11-27 10:32 ` Kevin Wolf
2020-11-27 12:21 ` Markus Armbruster
2020-11-27 15:25 ` Kevin Wolf
2020-11-27 16:52 ` Markus Armbruster
2020-11-30 17:36 ` Daniel P. Berrangé
2020-11-30 17:24 ` 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=87r1ofru4z.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=dplotnikov@virtuozzo.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.