From: Eric Blake <eblake@redhat.com> To: Denis Plotnikov <dplotnikov@virtuozzo.com>, kwolf@redhat.com, mreitz@redhat.com Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, den@virtuozzo.com Subject: Re: [Qemu-devel] [PATCH] [RFC] qcow2: add compression type feature Date: Tue, 30 Apr 2019 09:56:20 -0500 [thread overview] Message-ID: <dd8e89d4-b9eb-da1f-5afa-52c3399cf7e5@redhat.com> (raw) In-Reply-To: <20190205090825.14059-1-dplotnikov@virtuozzo.com> [-- Attachment #1: Type: text/plain, Size: 1801 bytes --] On 2/5/19 3:08 AM, Denis Plotnikov wrote: > The patch adds some preparation parts for incompatible compression type > feature into QCOW2 header that indicates that *all* compressed clusters > must be (de)compressed using a certain compression type. > > It is implied that the compression type is set on the image creation and > can be changed only later by image convertion, thus the only compression s/convertion/conversion/ > algorithm is used for the image. > > The plan is to add support for ZSTD and then may be something more effective > in the future. > > ZSDT compression algorithm consumes 3-5 times less CPU power with a s/ZSDT/ZSTD/ > comparable comression ratio with zlib. It would be wise to use it for s/comression/compression/ > data compression f.e. for backups. > > The default compression is ZLIB. > > Signed-off-by: Denis Plotnikov <dplotnikov@virtuozzo.com> > --- > block/qcow2.c | 25 +++++++++++++++++++++++++ > block/qcow2.h | 26 ++++++++++++++++++++++---- > 2 files changed, 47 insertions(+), 4 deletions(-) > > diff --git a/block/qcow2.c b/block/qcow2.c > index 8c91b92865..cb3d6cc1c0 100644 > --- a/block/qcow2.c > +++ b/block/qcow2.c > @@ -73,6 +73,7 @@ typedef struct { > #define QCOW2_EXT_MAGIC_FEATURE_TABLE 0x6803f857 > #define QCOW2_EXT_MAGIC_CRYPTO_HEADER 0x0537be77 > #define QCOW2_EXT_MAGIC_BITMAPS 0x23852875 > +#define QCOW2_EXT_MAGIC_COMPRESSION_TYPE 0x434D5052 This appears to be adding a new header extension magic number, but didn't actually modify the specification. I'd expect this patch to touch docs/interop/qcow2.txt before it can be considered complete. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Eric Blake <eblake@redhat.com> To: Denis Plotnikov <dplotnikov@virtuozzo.com>, kwolf@redhat.com, mreitz@redhat.com Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, den@virtuozzo.com Subject: Re: [Qemu-devel] [PATCH] [RFC] qcow2: add compression type feature Date: Tue, 30 Apr 2019 09:56:20 -0500 [thread overview] Message-ID: <dd8e89d4-b9eb-da1f-5afa-52c3399cf7e5@redhat.com> (raw) Message-ID: <20190430145620.1z04w2BkeKBKDEJq93BxRloVD84suhpJJ-jLtlaO1U4@z> (raw) In-Reply-To: <20190205090825.14059-1-dplotnikov@virtuozzo.com> [-- Attachment #1: Type: text/plain, Size: 1801 bytes --] On 2/5/19 3:08 AM, Denis Plotnikov wrote: > The patch adds some preparation parts for incompatible compression type > feature into QCOW2 header that indicates that *all* compressed clusters > must be (de)compressed using a certain compression type. > > It is implied that the compression type is set on the image creation and > can be changed only later by image convertion, thus the only compression s/convertion/conversion/ > algorithm is used for the image. > > The plan is to add support for ZSTD and then may be something more effective > in the future. > > ZSDT compression algorithm consumes 3-5 times less CPU power with a s/ZSDT/ZSTD/ > comparable comression ratio with zlib. It would be wise to use it for s/comression/compression/ > data compression f.e. for backups. > > The default compression is ZLIB. > > Signed-off-by: Denis Plotnikov <dplotnikov@virtuozzo.com> > --- > block/qcow2.c | 25 +++++++++++++++++++++++++ > block/qcow2.h | 26 ++++++++++++++++++++++---- > 2 files changed, 47 insertions(+), 4 deletions(-) > > diff --git a/block/qcow2.c b/block/qcow2.c > index 8c91b92865..cb3d6cc1c0 100644 > --- a/block/qcow2.c > +++ b/block/qcow2.c > @@ -73,6 +73,7 @@ typedef struct { > #define QCOW2_EXT_MAGIC_FEATURE_TABLE 0x6803f857 > #define QCOW2_EXT_MAGIC_CRYPTO_HEADER 0x0537be77 > #define QCOW2_EXT_MAGIC_BITMAPS 0x23852875 > +#define QCOW2_EXT_MAGIC_COMPRESSION_TYPE 0x434D5052 This appears to be adding a new header extension magic number, but didn't actually modify the specification. I'd expect this patch to touch docs/interop/qcow2.txt before it can be considered complete. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-04-30 14:56 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-02-05 9:08 [Qemu-devel] [PATCH] [RFC] qcow2: add compression type feature Denis Plotnikov 2019-04-28 22:32 ` Max Reitz 2019-04-28 22:32 ` Max Reitz 2019-05-16 7:50 ` Denis Plotnikov 2019-05-16 10:40 ` Max Reitz 2019-05-16 10:56 ` Denis Plotnikov 2019-04-30 9:58 ` Stefano Garzarella 2019-04-30 9:58 ` Stefano Garzarella 2019-04-30 14:56 ` Eric Blake [this message] 2019-04-30 14:56 ` Eric Blake
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=dd8e89d4-b9eb-da1f-5afa-52c3399cf7e5@redhat.com \ --to=eblake@redhat.com \ --cc=den@virtuozzo.com \ --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: linkBe 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).