qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Denis Plotnikov <dplotnikov@virtuozzo.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, berto@igalia.com, qemu-block@nongnu.org,
	armbru@redhat.com, mreitz@redhat.com, den@openvz.org
Subject: Re: [PATCH v4 5/5] iotests: 287: add qcow2 compression type test
Date: Wed, 4 Mar 2020 14:27:46 +0300	[thread overview]
Message-ID: <3d79452c-a2e9-06f5-ebf1-5edb3ac24108@virtuozzo.com> (raw)
In-Reply-To: <20200303133425.24471-6-dplotnikov@virtuozzo.com>

03.03.2020 16:34, Denis Plotnikov wrote:
> The test checks fulfilling qcow2 requiriements for the compression
> type feature and zstd compression type operability.
> 
> Signed-off-by: Denis Plotnikov <dplotnikov@virtuozzo.com>
> ---
>   tests/qemu-iotests/287     | 127 +++++++++++++++++++++++++++++++++++++
>   tests/qemu-iotests/287.out |  43 +++++++++++++
>   tests/qemu-iotests/group   |   1 +
>   3 files changed, 171 insertions(+)
>   create mode 100755 tests/qemu-iotests/287
>   create mode 100644 tests/qemu-iotests/287.out
> 
> diff --git a/tests/qemu-iotests/287 b/tests/qemu-iotests/287
> new file mode 100755
> index 0000000000..39cb665c85
> --- /dev/null
> +++ b/tests/qemu-iotests/287

[..]

> +# Test: using zstd compression, write to and read from an image
> +echo
> +echo "=== Testing reading and writing with zstd ==="
> +echo
> +
> +CLUSTER_SIZE=65536
> +IMGOPTS='compression_type=zstd' _make_test_img 64M

As I understand, you should define env variable assignments on the same line
with _make_test_img so that they be passed to it, like
CLUSTER_SIZE=65536 IMGOPTS='compression_type=zstd' _make_test_img 64M

with this:
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>

> +$QEMU_IO -c "write -c -P 0xAC 65536 64k " "$TEST_IMG" | _filter_qemu_io

you may s/65536/64k/

> +$QEMU_IO -c "read -P 0xAC 65536 65536 " "$TEST_IMG" | _filter_qemu_io
> +$QEMU_IO -c "read -v 131070 8 " "$TEST_IMG" | _filter_qemu_io
> +$QEMU_IO -c "read -v 65534 8" "$TEST_IMG" | _filter_qemu_io
> +


[..]


-- 
Best regards,
Vladimir


  reply	other threads:[~2020-03-04 11:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 13:34 [PATCH v4 0/5] qcow2: Implement zstd cluster compression method Denis Plotnikov
2020-03-03 13:34 ` [PATCH v4 1/5] block/qcow2-threads: fix qcow2_decompress Denis Plotnikov
2020-03-03 13:34 ` [PATCH v4 2/5] qcow2: introduce compression type feature Denis Plotnikov
2020-03-03 14:32   ` Vladimir Sementsov-Ogievskiy
2020-03-03 13:34 ` [PATCH v4 3/5] qcow2: rework the cluster compression routine Denis Plotnikov
2020-03-03 15:43   ` Vladimir Sementsov-Ogievskiy
2020-03-04  7:46   ` Vladimir Sementsov-Ogievskiy
2020-03-03 13:34 ` [PATCH v4 4/5] qcow2: add zstd cluster compression Denis Plotnikov
2020-03-03 14:41   ` Markus Armbruster
2020-03-04  7:49   ` Vladimir Sementsov-Ogievskiy
2020-03-04 12:46     ` Denis Plotnikov
2020-03-03 13:34 ` [PATCH v4 5/5] iotests: 287: add qcow2 compression type test Denis Plotnikov
2020-03-04 11:27   ` Vladimir Sementsov-Ogievskiy [this message]
2020-03-04 13:01     ` 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=3d79452c-a2e9-06f5-ebf1-5edb3ac24108@virtuozzo.com \
    --to=vsementsov@virtuozzo.com \
    --cc=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 \
    /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).