From: Markus Armbruster <armbru@redhat.com>
To: Denis Plotnikov <dplotnikov@virtuozzo.com>
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com, berto@igalia.com,
qemu-block@nongnu.org, qemu-devel@nongnu.org, mreitz@redhat.com,
den@openvz.org
Subject: Re: [PATCH v9 1/4] qcow2: introduce compression type feature
Date: Mon, 30 Mar 2020 17:06:30 +0200 [thread overview]
Message-ID: <87imilubk9.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20200323142558.15473-2-dplotnikov@virtuozzo.com> (Denis Plotnikov's message of "Mon, 23 Mar 2020 17:25:55 +0300")
Denis Plotnikov <dplotnikov@virtuozzo.com> writes:
> The patch adds some preparation parts for incompatible compression type
> feature to qcow2 allowing the use different compression methods for
> image clusters (de)compressing.
>
> 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, and thus,
> for all image clusters.
>
> The goal of the feature is to add support of other compression methods
> to qcow2. For example, ZSTD which is more effective on compression than ZLIB.
>
> The default compression is ZLIB. Images created with ZLIB compression type
> are backward compatible with older qemu versions.
>
> Adding of the compression type breaks a number of tests because now the
> compression type is reported on image creation and there are some changes
> in the qcow2 header in size and offsets.
>
> The tests are fixed in the following ways:
> * filter out compression_type for many tests
> * fix header size, feature table size and backing file offset
> affected tests: 031, 036, 061, 080
> header_size +=8: 1 byte compression type
> 7 bytes padding
> feature_table += 48: incompatible feature compression type
> backing_file_offset += 56 (8 + 48 -> header_change + feature_table_change)
> * add "compression type" for test output matching when it isn't filtered
> affected tests: 049, 060, 061, 065, 144, 182, 242, 255
>
> Signed-off-by: Denis Plotnikov <dplotnikov@virtuozzo.com>
Hmm, haven't I've seen this before? ... Yes, I provided my QAPI part:
Acked-by for v5, and the QAPI part hasn't changed since. You can save
me a bit of labor by carrying my Acked-by forward.
Once again, QAPI part:
Acked-by: Markus Armbruster <armbru@redhat.com>
next prev parent reply other threads:[~2020-03-30 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 14:25 [PATCH v9 0/4] qcow2: Implement zstd cluster compression method Denis Plotnikov
2020-03-23 14:25 ` [PATCH v9 1/4] qcow2: introduce compression type feature Denis Plotnikov
2020-03-23 15:59 ` Vladimir Sementsov-Ogievskiy
2020-03-30 15:06 ` Markus Armbruster [this message]
2020-03-30 15:16 ` Denis Plotnikov
2020-03-23 14:25 ` [PATCH v9 2/4] qcow2: rework the cluster compression routine Denis Plotnikov
2020-03-23 14:25 ` [PATCH v9 3/4] qcow2: add zstd cluster compression Denis Plotnikov
2020-03-27 8:43 ` Vladimir Sementsov-Ogievskiy
2020-03-27 9:40 ` Denis Plotnikov
2020-03-27 11:40 ` Vladimir Sementsov-Ogievskiy
2020-03-23 14:25 ` [PATCH v9 4/4] iotests: 287: add qcow2 compression type test 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=87imilubk9.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=berto@igalia.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 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.