On 04/27/2016 10:59 AM, Fam Zheng wrote:
On Wed, 04/27 09:32, Denis V. Lunev wrote:
On 04/26/2016 12:46 PM, Stefan Hajnoczi wrote:
On Sat, Apr 23, 2016 at 11:41:51AM +0300, Denis V. Lunev wrote:
The idea is simple - backup is "written-once" data. It is written block
by block and it is large en
Am 27.04.2016 um 09:59 hat Fam Zheng geschrieben:
> On Wed, 04/27 09:32, Denis V. Lunev wrote:
> > On 04/26/2016 12:46 PM, Stefan Hajnoczi wrote:
> > > On Sat, Apr 23, 2016 at 11:41:51AM +0300, Denis V. Lunev wrote:
> > > > The idea is simple - backup is "written-once" data. It is written block
> >
On Wed, 04/27 09:32, Denis V. Lunev wrote:
> On 04/26/2016 12:46 PM, Stefan Hajnoczi wrote:
> > On Sat, Apr 23, 2016 at 11:41:51AM +0300, Denis V. Lunev wrote:
> > > 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 sa
On 04/26/2016 12:46 PM, Stefan Hajnoczi wrote:
On Sat, Apr 23, 2016 at 11:41:51AM +0300, Denis V. Lunev wrote:
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.
These patches add the a
On Sat, Apr 23, 2016 at 11:41:51AM +0300, Denis V. Lunev wrote:
> 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.
>
> These patches add the ability to compress data during backup. T
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.
These patches add the ability to compress data during backup. This
functionality is implemented by means of adding options to the qmp/hmp
