From: Orit Wasserman <owasserm@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: blauwirbel@gmail.com, qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 8/9] QMP commands changes
Date: Tue, 03 Jan 2012 17:57:02 +0200 [thread overview]
Message-ID: <4F03254E.5020204@redhat.com> (raw)
In-Reply-To: <CAJSP0QUtOidhXSZvGB2noAqOqoRObgDU6U+brrrz5_-ncmWoxw@mail.gmail.com>
On 01/03/2012 05:47 PM, Stefan Hajnoczi wrote:
> On Tue, Jan 3, 2012 at 3:34 PM, Orit Wasserman <owasserm@redhat.com> wrote:
>> + .args_type = "detach:-d,blk:-b,inc:-i,xbrle:-x,uri:s",
>> + .params = "[-d] [-b] [-i] [-x] uri",
>> + .help = "migrate to URI"
>> + "\n\t -d to not wait for completion"
>> + "\n\t -b for migration without shared storage with"
>> + " full copy of disk"
>> + "\n\t -i for migration without"
>> + " shared storage with incremental copy of disk"
>> + " (base image shared between source and destination)"
>> + "\n\t -x to use XBRLE page delta compression",
>
> It's too bad that this algorithm is user-visible and needs to be
> expicitly enabled/disabled. I think it would be useful in a much
> wider range of cases if the trade-offs were understood well enough so
> that QEMU can include a threshold or heuristic which chooses the
> migration algorithm behind the scenes.
I agree that an automatic switching on/off XBRLE is very desirable.
At the first phase we merge it as a user option, and the in the next phase will be adding
the part that switch it on/off.
>
> I'm afraid that locking XBRLE behind an explicit option means we're
> merging dead code. What do you think?
Even as a user option this option will be useful , in many cases users are aware of
their workload and can set this option on.
Orit
>
> Stefan
next prev parent reply other threads:[~2012-01-03 15:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 15:34 [Qemu-devel] [PATCH v5 0/9] XBZRLE delta for live migration of large memory apps Orit Wasserman
2012-01-03 15:34 ` [Qemu-devel] [PATCH v5 1/9] Add cache handling functions Orit Wasserman
2012-01-03 19:54 ` Anthony Liguori
2012-01-04 9:29 ` Orit Wasserman
2012-01-04 22:20 ` Michael Roth
2012-01-04 11:46 ` Stefan Hajnoczi
2012-01-04 13:27 ` Orit Wasserman
2012-01-03 15:34 ` [Qemu-devel] [PATCH v5 2/9] Add rle_encode and rle_decode functions Implement Run Length Encoding compression Orit Wasserman
2012-01-03 19:57 ` Anthony Liguori
2012-01-04 9:31 ` Orit Wasserman
2012-01-04 16:52 ` Paolo Bonzini
2012-01-04 12:59 ` Avi Kivity
2012-01-04 13:35 ` Stefan Hajnoczi
2012-01-04 13:45 ` Avi Kivity
2012-01-03 15:34 ` [Qemu-devel] [PATCH v5 3/9] Add save_block_hdr function Orit Wasserman
2012-01-03 15:34 ` [Qemu-devel] [PATCH v5 4/9] Add host_from_stream_offset_versioned function Orit Wasserman
2012-01-04 12:00 ` Stefan Hajnoczi
2012-01-04 20:59 ` Michael Roth
2012-01-03 15:34 ` [Qemu-devel] [PATCH v5 5/9] Add XBRLE to ram_save_block and ram_save_live Orit Wasserman
2012-01-04 12:14 ` Stefan Hajnoczi
2012-01-04 13:29 ` Orit Wasserman
2012-01-03 15:34 ` [Qemu-devel] [PATCH v5 6/9] Add xbrle parameters to MigrationState Orit Wasserman
2012-01-04 21:17 ` Michael Roth
2012-01-03 15:34 ` [Qemu-devel] [PATCH v5 7/9] Add set_cachesize to change XBRLE cache size Orit Wasserman
2012-01-03 15:34 ` [Qemu-devel] [PATCH v5 8/9] QMP commands changes Orit Wasserman
2012-01-03 15:47 ` Stefan Hajnoczi
2012-01-03 15:57 ` Orit Wasserman [this message]
2012-01-03 16:20 ` Stefan Hajnoczi
2012-01-03 15:34 ` [Qemu-devel] [PATCH v5 9/9] Add XBRLE statistics information Orit Wasserman
2012-01-04 22:45 ` Michael Roth
2012-01-07 16:31 ` Blue Swirl
2012-01-03 16:32 ` [Qemu-devel] [PATCH v5 0/9] XBZRLE delta for live migration of large memory apps Anthony Liguori
2012-01-03 17:02 ` Orit Wasserman
2012-01-04 13:02 ` Avi Kivity
2012-01-04 16:03 ` Orit Wasserman
-- strict thread matches above, loose matches on Subject: below --
2012-01-03 13:35 Orit Wasserman
2012-01-03 13:35 ` [Qemu-devel] [PATCH v5 8/9] QMP commands changes Orit Wasserman
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=4F03254E.5020204@redhat.com \
--to=owasserm@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--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).