> Am 24.02.2017 um 16:02 schrieb Kevin Wolf :
>
> Am 21.02.2017 um 13:29 hat Peter Lieven geschrieben:
>> the convert process is currently completely implemented with sync operations.
>> That means it reads one buffer and then writes it. No parallelism and each
>> sync
>> request takes as long a
Am 21.02.2017 um 13:29 hat Peter Lieven geschrieben:
> the convert process is currently completely implemented with sync operations.
> That means it reads one buffer and then writes it. No parallelism and each
> sync
> request takes as long as it takes until it is completed.
>
> This can be a big
Am 22.02.2017 um 16:31 schrieb Stefan Hajnoczi:
On Tue, Feb 21, 2017 at 01:29:51PM +0100, Peter Lieven wrote:
the convert process is currently completely implemented with sync operations.
That means it reads one buffer and then writes it. No parallelism and each sync
request takes as long as it
On Tue, Feb 21, 2017 at 01:29:51PM +0100, Peter Lieven wrote:
> the convert process is currently completely implemented with sync operations.
> That means it reads one buffer and then writes it. No parallelism and each
> sync
> request takes as long as it takes until it is completed.
>
> This can
Hi,
This series failed build test on s390x host. Please find the details below.
Type: series
Subject: [Qemu-devel] [PATCH] qemu-img: make convert async
Message-id: 1487680191-13096-1-git-send-email...@kamp.de
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked under the git
the convert process is currently completely implemented with sync operations.
That means it reads one buffer and then writes it. No parallelism and each sync
request takes as long as it takes until it is completed.
This can be a big performance hit when the convert process reads and writes
to devi
