From: Max Reitz <mreitz@redhat.com>
To: Denis Plotnikov <dplotnikov@virtuozzo.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com, berto@igalia.com,
qemu-block@nongnu.org, armbru@redhat.com, den@openvz.org
Subject: Re: [PATCH v23 0/4] implement zstd cluster compression method
Date: Tue, 5 May 2020 14:03:07 +0200 [thread overview]
Message-ID: <ebc9d7e5-af1b-fee8-b76f-fb6bc75dc987@redhat.com> (raw)
In-Reply-To: <8f4de4c5-f88d-5693-2327-309ccfc325ff@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 691 bytes --]
On 05.05.20 12:26, Max Reitz wrote:
> On 30.04.20 12:19, Denis Plotnikov wrote:
>> v23:
>> Undecided: whether to add zstd(zlib) compression
>> details to the qcow2 spec
>> 03: tighten assertion on zstd decompression [Eric]
>> 04: use _rm_test_img appropriately [Max]
>
> Thanks, applied to my block branch:
I’m afraid I have to unqueue this series again, because it makes many
iotests fail due to an additional “compression_type=zlib” output when
images are created, an additional “compression type” line in
qemu-img info output where format-specific information is not
suppressed, and an additional line in qemu-img create -f qcow2 -o help.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-05-05 12:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 10:19 [PATCH v23 0/4] implement zstd cluster compression method Denis Plotnikov
2020-04-30 10:19 ` [PATCH v23 1/4] qcow2: introduce compression type feature Denis Plotnikov
2020-04-30 10:19 ` [PATCH v23 2/4] qcow2: rework the cluster compression routine Denis Plotnikov
2020-04-30 10:19 ` [PATCH v23 3/4] qcow2: add zstd cluster compression Denis Plotnikov
2020-04-30 10:19 ` [PATCH v23 4/4] iotests: 287: add qcow2 compression type test Denis Plotnikov
2020-05-05 10:26 ` [PATCH v23 0/4] implement zstd cluster compression method Max Reitz
2020-05-05 12:03 ` Max Reitz [this message]
2020-05-06 8:01 ` Denis Plotnikov
2020-05-06 8: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=ebc9d7e5-af1b-fee8-b76f-fb6bc75dc987@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=den@openvz.org \
--cc=dplotnikov@virtuozzo.com \
--cc=kwolf@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).