qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Denis Plotnikov <dplotnikov@virtuozzo.com>
To: Max Reitz <mreitz@redhat.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: Wed, 6 May 2020 11:01:48 +0300	[thread overview]
Message-ID: <e839211c-ae2b-4227-8e69-a9174eb13ffe@virtuozzo.com> (raw)
In-Reply-To: <ebc9d7e5-af1b-fee8-b76f-fb6bc75dc987@redhat.com>



On 05.05.2020 15:03, Max Reitz wrote:
> 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
>

Hmm, this is strange. I made some modifications for the tests
in 0001 of the series (qcow2: introduce compression type feature).

Among the other test related changes, the patch contains the hunk:

+++ b/tests/qemu-iotests/common.filter
@@ -152,7 +152,8 @@ _filter_img_create()
          -e "s# refcount_bits=[0-9]\\+##g" \
          -e "s# key-secret=[a-zA-Z0-9]\\+##g" \
          -e "s# iter-time=[0-9]\\+##g" \
-        -e "s# force_size=\\(on\\|off\\)##g"
+        -e "s# force_size=\\(on\\|off\\)##g" \
+        -e "s# compression_type=[a-zA-Z0-9]\\+##g"
  }

which has to filter out "compression_type" on image creation.

But you say that you can see the "compression_type" on the image creation.
May be the patch wasn't fully applied? Or the test related modification 
were omitted?

I've just re-based the series on top of:

681b07f4e76dbb700c16918d (vanilla/master, mainstream)
Merge: a2261b2754 714eb0dbc5
Author: Peter Maydell <peter.maydell@linaro.org>
Date:   Tue May 5 15:47:44 2020 +0100

and run the tests with 'make check-block'

and got the following:

Not run: 071 099 184 220 259 267
Some cases not run in: 030 040 041
Passed all 113 iotests

May be I do something wrong?

Denis


  reply	other threads:[~2020-05-06  8:03 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
2020-05-06  8:01     ` Denis Plotnikov [this message]
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=e839211c-ae2b-4227-8e69-a9174eb13ffe@virtuozzo.com \
    --to=dplotnikov@virtuozzo.com \
    --cc=armbru@redhat.com \
    --cc=berto@igalia.com \
    --cc=den@openvz.org \
    --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).