On 24.06.2016 18:39, Eric Blake wrote:
On 06/23/2016 03:15 AM, Pavel Butsykin wrote:
@@ -3309,6 +3315,7 @@ void qmp_drive_backup(const char *device, const
char *target,
bool has_mode, enum NewImageMode mode,
bool has_speed, int64_t speed,
On 06/23/2016 03:15 AM, Pavel Butsykin wrote:
>>> @@ -3309,6 +3315,7 @@ void qmp_drive_backup(const char *device, const
>>> char *target,
>>> bool has_mode, enum NewImageMode mode,
>>> bool has_speed, int64_t speed,
>>> bool h
On 13.06.2016 23:18, Eric Blake wrote:
On 05/31/2016 03:15 AM, Denis V. Lunev wrote:
From: Pavel Butsykin
The idea is simple - backup is "written-once" data. It is written block
by block and it is large enough. It would be nice to save storage
space and compress it.
The patch adds a flag to t
On 05/31/2016 03:15 AM, Denis V. Lunev wrote:
> From: Pavel Butsykin
>
> The idea is simple - backup is "written-once" data. It is written block
> by block and it is large enough. It would be nice to save storage
> space and compress it.
>
> The patch adds a flag to the qmp/hmp drive-backup comm
On Tue, May 31, 2016 at 12:15:27PM +0300, Denis V. Lunev wrote:
> From: Pavel Butsykin
>
> The idea is simple - backup is "written-once" data. It is written block
> by block and it is large enough. It would be nice to save storage
> space and compress it.
>
> The patch adds a flag to the qmp/hmp
From: Pavel Butsykin
The idea is simple - backup is "written-once" data. It is written block
by block and it is large enough. It would be nice to save storage
space and compress it.
The patch adds a flag to the qmp/hmp drive-backup command which enables
block compression. Compression should be i
