From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: den@openvz.org,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [PATCH RFC] meson: add option to use zstd for qcow2 compression by default
Date: Mon, 21 Jun 2021 17:59:43 +0200 [thread overview]
Message-ID: <YNC3b3S8tLM47PJn@redhat.com> (raw)
In-Reply-To: <8d3711a0-2716-3bc5-3710-990042e16c0b@redhat.com>
Am 21.06.2021 um 10:22 hat Paolo Bonzini geschrieben:
> On 17/06/21 21:51, Vladimir Sementsov-Ogievskiy wrote:
> > So, it's an RFC. I also can split the patch so that refactoring of
> > qcow2_co_create() go in a separate preparation patch.
> >
> > Another RFC question, shouldn't we move to zstd by default in upstream
> > too?
>
> I think backwards-incompatible changes in the past were not handled with
> build options, but that can be changed.
>
> However I would prefer to have an option like
> --with-qcow2-compression={zstd,zlib}. Meson supports multiple-choice
> options, they don't have to use enabled/disabled or (if boolean) true/false.
Yes, this is more extensible.
> Regarding changing the default, that would make images unreadable to QEMU
> 5.0 and earlier versions. Does that apply to images that have no compressed
> clusters?
I think it does because you could be writing compressed clusters to it
later. Originally, we had only 'qemu-img convert -c' that could write
compressed clusters, but today the backup job can write them, too, and
it doesn't create the image file itself.
Kevin
next prev parent reply other threads:[~2021-06-21 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 19:51 [PATCH RFC] meson: add option to use zstd for qcow2 compression by default Vladimir Sementsov-Ogievskiy
2021-06-19 14:13 ` Vladimir Sementsov-Ogievskiy
2021-06-21 8:22 ` Paolo Bonzini
2021-06-21 15:59 ` Kevin Wolf [this message]
2021-06-22 10:16 ` Vladimir Sementsov-Ogievskiy
2021-06-22 10:20 ` Paolo Bonzini
2021-07-01 9:54 ` Vladimir Sementsov-Ogievskiy
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=YNC3b3S8tLM47PJn@redhat.com \
--to=kwolf@redhat.com \
--cc=den@openvz.org \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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).