From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
"Shribman, Aidan" <aidan.shribman@sap.com>,
qemu-devel Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3] XBZRLE delta for live migration of large memory apps
Date: Wed, 03 Aug 2011 01:38:58 +0300 [thread overview]
Message-ID: <4E387C82.8080908@redhat.com> (raw)
In-Reply-To: <B5189056-4BF7-4B17-B887-AE2E803EA005@suse.de>
On 08/02/2011 05:01 PM, Alexander Graf wrote:
> So if I understand correctly, this enabled delta updates for dirty pages? Would it be possible to do the same on the block layer, so that VM backing file data could potentially save the new information as delta over the old block? Especially with metadata updates, that could save quite some disk space.
Just use a smaller block size. While you could save even more when
considering metadata, I think the bulk of the gain would be in actual data.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2011-08-02 22:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 13:45 [Qemu-devel] [PATCH v3] XBZRLE delta for live migration of large memory apps Shribman, Aidan
2011-08-02 14:01 ` Alexander Graf
2011-08-02 14:34 ` Paolo Bonzini
2011-08-02 15:00 ` Anthony Liguori
2011-08-04 9:31 ` Shribman, Aidan
2011-08-02 18:08 ` Stefan Hajnoczi
2011-08-02 22:38 ` Avi Kivity [this message]
2011-08-02 18:05 ` Stefan Hajnoczi
2011-08-08 8:42 ` Shribman, Aidan
2011-08-08 14:02 ` Stefan Hajnoczi
2011-08-02 20:43 ` Blue Swirl
2011-08-08 8:42 ` Shribman, Aidan
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=4E387C82.8080908@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=aidan.shribman@sap.com \
--cc=kwolf@redhat.com \
--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 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).