qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, hreitz@redhat.com,
	fam@euphon.net, eblake@redhat.com, vsementsov@yandex-team.ru,
	den@virtuozzo.com
Subject: Re: [PATCH v2 0/3] qemu-img: map: implement support for compressed clusters
Date: Mon, 31 Jul 2023 17:45:31 +0300	[thread overview]
Message-ID: <b847bd77-d23d-c0e4-dbb5-e69dba0d2db8@virtuozzo.com> (raw)
In-Reply-To: <8c0bc7da-175d-a367-3d7d-32f570953e7c@virtuozzo.com>

On 7/24/23 16:10, Andrey Drobyshev wrote:
> On 7/6/23 19:30, Andrey Drobyshev wrote:
>> v1 --> v2:
>>   * Add vmdk format to the 1st commit.  Tweak commit message accordingly;
>>   * Make "compressed" field in MapEntry optional.
>>
>> v1: https://lists.nongnu.org/archive/html/qemu-block/2023-06/msg00184.html
>>
>> Andrey Drobyshev (3):
>>   block: add BDRV_BLOCK_COMPRESSED flag for bdrv_block_status()
>>   qemu-img: map: report compressed data blocks
>>   qemu-iotests: update expected tests output to contain "compressed"
>>     field
>>
>>  block/qcow.c                                  |   5 +-
>>  block/qcow2.c                                 |   3 +
>>  block/vmdk.c                                  |   2 +
>>  include/block/block-common.h                  |   3 +
>>  qapi/block-core.json                          |   7 +-
>>  qemu-img.c                                    |  16 +-
>>  tests/qemu-iotests/122.out                    |  84 ++++----
>>  tests/qemu-iotests/154.out                    | 194 +++++++++---------
>>  tests/qemu-iotests/179.out                    | 178 ++++++++--------
>>  tests/qemu-iotests/244.out                    |  24 +--
>>  tests/qemu-iotests/252.out                    |  10 +-
>>  tests/qemu-iotests/274.out                    |  48 ++---
>>  .../tests/nbd-qemu-allocation.out             |   6 +-
>>  13 files changed, 302 insertions(+), 278 deletions(-)
>>
> 
> Ping

Yet another ping


  reply	other threads:[~2023-07-31 14:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 16:30 [PATCH v2 0/3] qemu-img: map: implement support for compressed clusters Andrey Drobyshev via
2023-07-06 16:30 ` [PATCH v2 1/3] block: add BDRV_BLOCK_COMPRESSED flag for bdrv_block_status() Andrey Drobyshev via
2023-07-12  7:13   ` Denis V. Lunev
2023-08-25 14:14   ` Hanna Czenczek
2023-07-06 16:30 ` [PATCH v2 2/3] qemu-img: map: report compressed data blocks Andrey Drobyshev via
2023-07-12  7:14   ` Denis V. Lunev
2023-08-25 14:14   ` Hanna Czenczek
2023-08-29  6:44     ` Andrey Drobyshev
2023-08-29  8:46       ` Hanna Czenczek
2023-07-06 16:30 ` [PATCH v2 3/3] qemu-iotests: update expected tests output to contain "compressed" field Andrey Drobyshev via
2023-07-12  7:14   ` Denis V. Lunev
2023-07-24 13:10 ` [PATCH v2 0/3] qemu-img: map: implement support for compressed clusters Andrey Drobyshev
2023-07-31 14:45   ` Andrey Drobyshev [this message]
2023-08-16  9:22     ` Andrey Drobyshev
2023-08-22 17:35       ` Andrey Drobyshev

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=b847bd77-d23d-c0e4-dbb5-e69dba0d2db8@virtuozzo.com \
    --to=andrey.drobyshev@virtuozzo.com \
    --cc=den@virtuozzo.com \
    --cc=eblake@redhat.com \
    --cc=fam@euphon.net \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@yandex-team.ru \
    /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).