All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Peter Lieven <pl@kamp.de>,
	kwolf@redhat.com, famz@redhat.com, qemu-devel@nongnu.org,
	qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [RFC PATCH V4] qemu-img: make convert async
Date: Thu, 7 Jun 2018 13:19:29 +0300	[thread overview]
Message-ID: <2ddb8b13-650a-5bd7-8c77-3f2eca34efdf@virtuozzo.com> (raw)
In-Reply-To: <20180607101046.GC19032@stefanha-x1.localdomain>

07.06.2018 13:10, Stefan Hajnoczi wrote:
> On Fri, Jun 01, 2018 at 07:16:14PM +0300, Vladimir Sementsov-Ogievskiy wrote:
>> 20.02.2017 17:59, Peter Lieven wrote:
>>> Am 20.02.2017 um 15:50 schrieb Stefan Hajnoczi:
>>>> On Fri, Feb 17, 2017 at 05:00:24PM +0100, Peter Lieven wrote:
>>>>> this is something I have been thinking about for almost 2 years now.
>>>>> we heavily have the following two use cases when using qemu-img
>>>>> convert.
>>>>>
>>>>>
>> [...]
>>
>>>> Does this patch work with compressed images?  Especially the
>>>> out-of-order write mode may be problematic with a compressed qcow2
>>>> image.
>>> It does, but you are right, out-of-order writes and compression should
>>> be mutually exclusive.
>>
>> Sorry for being late, but can you please explain to me, why?
> There are image format-specific limitations on compressed writes.  For
> some reason I thought they were append-only in qcow2, but I was wrong.
>
> Stefan

And what are limitations for compressed writes in qcow2? We can't write 
asynchronously? Why?

-- 
Best regards,
Vladimir

  reply	other threads:[~2018-06-07 10:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 16:00 [Qemu-devel] [RFC PATCH V4] qemu-img: make convert async Peter Lieven
2017-02-20 14:50 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-02-20 14:59   ` Peter Lieven
2017-02-21 11:08     ` Stefan Hajnoczi
2018-06-01 16:16     ` Vladimir Sementsov-Ogievskiy
2018-06-07 10:10       ` Stefan Hajnoczi
2018-06-07 10:19         ` Vladimir Sementsov-Ogievskiy [this message]
2018-06-08  7:51           ` Stefan Hajnoczi

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=2ddb8b13-650a-5bd7-8c77-3f2eca34efdf@virtuozzo.com \
    --to=vsementsov@virtuozzo.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pl@kamp.de \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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 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.