From: Eric Blake <eblake@redhat.com>
To: Peter Lieven <pl@kamp.de>, qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, lersek@redhat.com,
den@openvz.org, mreitz@redhat.com, berrange@redhat.com
Subject: Re: [Qemu-devel] [PATCH V5 09/10] block/qcow2: add lzo compress format
Date: Tue, 25 Jul 2017 16:41:16 -0500 [thread overview]
Message-ID: <3b2bc845-2201-a813-ad4e-d3cf86666bbd@redhat.com> (raw)
In-Reply-To: <1500993699-19299-10-git-send-email-pl@kamp.de>
[-- Attachment #1: Type: text/plain, Size: 2128 bytes --]
On 07/25/2017 09:41 AM, Peter Lieven wrote:
> Signed-off-by: Peter Lieven <pl@kamp.de>
> ---
> block/qcow2-cluster.c | 15 +++++++++++++++
> block/qcow2.c | 25 ++++++++++++++++++++++++-
> configure | 2 +-
> docs/interop/qcow2.txt | 2 ++
> qapi/block-core.json | 15 ++++++++++++---
> qemu-img.texi | 1 +
> 6 files changed, 55 insertions(+), 5 deletions(-)
>
> +++ b/docs/interop/qcow2.txt
> @@ -335,6 +335,8 @@ The fields of the compress format extension are:
> deflate: Standard zlib deflate compression without
> compression header
>
> + lzo: LZO1X compression without additional header
> +
> 14: compress_level (uint8_t)
>
> 0 = default compress level (valid for all formats, default)
What do compress_level and compress_window have to be for lzo? (If they
are not useful, document that it must be 0 - which you've already done
for compress_level).
> +# @Qcow2CompressLZO:
> +#
> +# Since: 2.10
2.11
> +##
> +{ 'struct': 'Qcow2CompressLZO',
> + 'data': { } }
> +
> +##
> # @Qcow2Compress:
> #
> # Specifies the compression format and compression level that should
> @@ -2491,8 +2500,8 @@
> { 'union': 'Qcow2Compress',
> 'base': { 'format': 'Qcow2CompressFormat' },
> 'discriminator': 'format',
> - 'data': { 'deflate': 'Qcow2CompressDeflate' } }
> -
> + 'data': { 'deflate': 'Qcow2CompressDeflate',
> + 'lzo': 'Qcow2CompressLZO' } }
>
Was the loss of the blank line intentional?
> +++ b/qemu-img.texi
> @@ -682,6 +682,7 @@ The following options are available if support for the respective libraries
> has been enabled at compile time:
>
> deflate Uses standard zlib defalte compression
> + lzo Uses LZO1X compression
The .json file spelled it lzo1x; is there a difference implied by the
choice of capitalization?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-07-25 21:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 14:41 [Qemu-devel] [PATCH V5 00/10] add Qcow2 compress format extension Peter Lieven
2017-07-25 14:41 ` [Qemu-devel] [PATCH V5 01/10] specs/qcow2: add " Peter Lieven
2017-07-25 15:03 ` Eric Blake
2017-07-25 20:29 ` Peter Lieven
2017-07-25 21:01 ` Eric Blake
2017-09-11 14:22 ` Kevin Wolf
2017-09-18 10:09 ` Peter Lieven
2017-09-18 10:50 ` Kevin Wolf
2017-12-13 16:43 ` Peter Lieven
2017-07-25 14:41 ` [Qemu-devel] [PATCH V5 02/10] qapi/block-core: add Qcow2Compress parameters Peter Lieven
2017-07-25 21:21 ` Eric Blake
2017-07-25 14:41 ` [Qemu-devel] [PATCH V5 03/10] block/qcow2: parse compress create options Peter Lieven
2017-07-25 21:26 ` Eric Blake
2017-07-25 14:41 ` [Qemu-devel] [PATCH V5 04/10] qemu-img: add documentation for compress settings Peter Lieven
2017-07-25 21:34 ` Eric Blake
2017-07-25 14:41 ` [Qemu-devel] [PATCH V5 05/10] block/qcow2: read and write the compress format extension Peter Lieven
2017-07-25 14:41 ` [Qemu-devel] [PATCH V5 06/10] block/qcow2: simplify ret usage in qcow2_create Peter Lieven
2017-07-25 14:41 ` [Qemu-devel] [PATCH V5 07/10] block/qcow2: optimize qcow2_co_pwritev_compressed Peter Lieven
2017-07-25 14:41 ` [Qemu-devel] [PATCH V5 08/10] block/qcow2: start using the compress format extension Peter Lieven
2017-07-25 14:41 ` [Qemu-devel] [PATCH V5 09/10] block/qcow2: add lzo compress format Peter Lieven
2017-07-25 21:41 ` Eric Blake [this message]
2017-07-25 14:41 ` [Qemu-devel] [PATCH V5 10/10] block/qcow2: add compress info to image specific info Peter Lieven
2017-07-25 21:55 ` Eric Blake
2017-07-26 9:05 ` Peter Lieven
2017-08-03 18:59 ` Peter Lieven
2017-09-11 14:08 ` Kevin Wolf
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=3b2bc845-2201-a813-ad4e-d3cf86666bbd@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=den@openvz.org \
--cc=kwolf@redhat.com \
--cc=lersek@redhat.com \
--cc=mreitz@redhat.com \
--cc=pl@kamp.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.