From: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, fam@euphon.net, vsementsov@virtuozzo.com,
armbru@redhat.com, mreitz@redhat.com, stefanha@redhat.com,
andrey.shinkevich@virtuozzo.com, den@openvz.org
Subject: [PATCH v5 0/4] qcow2: advanced compression options
Date: Sun, 20 Oct 2019 23:37:04 +0300 [thread overview]
Message-ID: <1571603828-185910-1-git-send-email-andrey.shinkevich@virtuozzo.com> (raw)
New enhancements for writing compressed data to QCOW2 image.
v5: The new iotests cases were amended and 'qiov_offset' parameter
value in the function bdrv_driver_pwritev_compressed() invoked
from the bdrv_co_do_copy_on_readv() fixed to 0.
Discussed on the email thread with ID:
<1571243333-882302-1-git-send-email-andrey.shinkevich@virtuozzo.com>
v4:
The 'compression' support at the block generic layer has been
accumulated in the separate patch 1/4. A little code refactoring
was made.
v3:
Instead of introducing multiple key options for many drivers, the
'compression' option has been introduced at the block generic layer
as suggested by Roman Kagan. Discussed on the email thread with ID
<1570026166-748566-1-git-send-email-andrey.shinkevich@virtuozzo.com>
Andrey Shinkevich (4):
block: support compressed write at generic layer
qcow2: Allow writing compressed data of multiple clusters
tests/qemu-iotests: add case to write compressed data of multiple
clusters
tests/qemu-iotests: add case for block-stream compress
block.c | 20 ++++++++-
block/io.c | 13 ++++--
block/qcow2.c | 106 +++++++++++++++++++++++++++++++++------------
blockdev.c | 9 +++-
include/block/block.h | 1 +
include/block/block_int.h | 2 +
qapi/block-core.json | 5 ++-
qemu-options.hx | 6 ++-
tests/qemu-iotests/030 | 34 ++++++++++++++-
tests/qemu-iotests/030.out | 4 +-
tests/qemu-iotests/214 | 45 +++++++++++++++++++
tests/qemu-iotests/214.out | 14 ++++++
12 files changed, 220 insertions(+), 39 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-10-20 20:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 20:37 Andrey Shinkevich [this message]
2019-10-20 20:37 ` [PATCH v5 1/4] block: support compressed write at generic layer Andrey Shinkevich
2019-10-22 9:28 ` Max Reitz
2019-10-22 10:21 ` Andrey Shinkevich
2019-10-22 10:46 ` Vladimir Sementsov-Ogievskiy
2019-10-22 11:31 ` Max Reitz
2019-10-22 12:23 ` Vladimir Sementsov-Ogievskiy
2019-10-22 12:56 ` Max Reitz
2019-10-22 13:53 ` Andrey Shinkevich
2019-10-24 9:34 ` Max Reitz
2019-10-24 12:56 ` Andrey Shinkevich
2019-10-24 13:48 ` Max Reitz
2019-10-24 14:07 ` Andrey Shinkevich
2019-10-24 15:12 ` Max Reitz
2019-10-24 14:27 ` Andrey Shinkevich
2019-10-22 14:28 ` Vladimir Sementsov-Ogievskiy
2019-10-20 20:37 ` [PATCH v5 2/4] qcow2: Allow writing compressed data of multiple clusters Andrey Shinkevich
2019-10-20 20:37 ` [PATCH v5 3/4] tests/qemu-iotests: add case to write " Andrey Shinkevich
2019-10-20 20:37 ` [PATCH v5 4/4] tests/qemu-iotests: add case for block-stream compress Andrey Shinkevich
2019-10-22 9:28 ` Max Reitz
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=1571603828-185910-1-git-send-email-andrey.shinkevich@virtuozzo.com \
--to=andrey.shinkevich@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--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).