qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Denis Plotnikov <dplotnikov@virtuozzo.com>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
	Denis Lunev <den@virtuozzo.com>,
	"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"armbru@redhat.com" <armbru@redhat.com>,
	"mreitz@redhat.com" <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v0 3/3] qcow2: add zstd cluster compression
Date: Tue, 2 Jul 2019 16:37:09 +0200	[thread overview]
Message-ID: <20190702143709.GB7894@localhost.localdomain> (raw)
In-Reply-To: <5a970b37-ef08-3d53-3d53-3abb9c3e97e0@virtuozzo.com>

Am 02.07.2019 um 14:49 hat Denis Plotnikov geschrieben:
> On 28.06.2019 14:57, Kevin Wolf wrote:
> > Am 28.05.2019 um 16:37 hat Denis Plotnikov geschrieben:
> >> diff --git a/configure b/configure
> >> index 1c563a7027..c90716189c 100755
> >> --- a/configure
> >> +++ b/configure
> >> @@ -433,6 +433,7 @@ opengl_dmabuf="no"
> >>   cpuid_h="no"
> >>   avx2_opt=""
> >>   zlib="yes"
> >> +zstd="yes"
> > 
> > This should be zstd="" so that a missing library will automatically
> > disable it instead of producing an error. (Building QEMU without zlib is
> > impossible, but building it without ZSTD should work.)
> But if we add zstd for clusters compression we have to build with zstd 
> each time. If we want to chose whether we want to build zstd we need to
> enclose all zstd related code with "ifdef"-s.
> I don't think it's good because we can end up with mess of version 
> supporting and not supporting zstd compression.

Yes, we'll need ifdefs. Or we could do it like the dmg compression
formats, a spearate source file for zstd that is compiled conditionally.

Anyway, I don't think making zstd a hard dependency for qemu is
acceptable.

> Another point is what the benefit of building qemu without zstd support 
> is since it's available and provides better performance than zlib (i.e. 
> the replacement for zlib) ?

Is it available in all relevant distros and even non-Linux platforms
that we support?

Another reason for wanting to compile it out even when it is available
is startup time. Each shared library to be loaded takes some time, and
there are use cases where you want a minimal guest to boot up really
fast.

Kevin


  reply	other threads:[~2019-07-02 14:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-28 14:37 [Qemu-devel] [PATCH v0 0/3] add zstd cluster compression Denis Plotnikov
2019-05-28 14:37 ` [Qemu-devel] [PATCH v0 1/3] qcow2: introduce compression type feature Denis Plotnikov
2019-05-29 11:40   ` Vladimir Sementsov-Ogievskiy
2019-06-28  9:45     ` Kevin Wolf
2019-06-27 16:35   ` Markus Armbruster
2019-06-28  9:54   ` Kevin Wolf
2019-06-28 11:07     ` Denis Plotnikov
2019-06-28 10:10   ` Kevin Wolf
2019-05-28 14:37 ` [Qemu-devel] [PATCH v0 2/3] qcow2: add compression type processing Denis Plotnikov
2019-05-29  9:47   ` Vladimir Sementsov-Ogievskiy
2019-06-28 10:23   ` Kevin Wolf
2019-06-28 11:24     ` Denis Plotnikov
2019-06-28 12:06       ` Kevin Wolf
2019-06-28 12:56         ` Denis Plotnikov
2019-06-28 14:24           ` Kevin Wolf
2019-06-28 14:40             ` Denis Plotnikov
2019-06-28 14:54               ` Kevin Wolf
2019-06-28 15:03                 ` Max Reitz
2019-06-28 15:14                   ` Denis Plotnikov
2019-06-28 19:34                 ` Eric Blake
2019-07-02 12:34                   ` Denis Plotnikov
2019-05-28 14:37 ` [Qemu-devel] [PATCH v0 3/3] qcow2: add zstd cluster compression Denis Plotnikov
2019-06-28 11:57   ` Kevin Wolf
2019-07-02 12:33     ` Denis Plotnikov
2019-07-02 12:49     ` Denis Plotnikov
2019-07-02 14:37       ` Kevin Wolf [this message]
2019-07-02 14:48         ` Denis Plotnikov
2019-06-04  7:56 ` [Qemu-devel] [PING] [PATCH v0 0/3] " Denis Plotnikov
2019-06-27 15:04   ` [Qemu-devel] [PING PING] " Denis Plotnikov

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=20190702143709.GB7894@localhost.localdomain \
    --to=kwolf@redhat.com \
    --cc=armbru@redhat.com \
    --cc=den@virtuozzo.com \
    --cc=dplotnikov@virtuozzo.com \
    --cc=mreitz@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).