From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Shribman, Aidan" <aidan.shribman@sap.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] XBRLE page delta compression for live migration of large memory apps
Date: Tue, 2 Aug 2011 16:53:33 +0100 [thread overview]
Message-ID: <CAJSP0QV6UxAz9e_6o13On2NWWnGb4P7CsFQ0UToPWhVZBaBpuA@mail.gmail.com> (raw)
In-Reply-To: <AB5A8C7661872E428D6B8E1C2DFA35085D848B5981@DEWDFECCR02.wdf.sap.corp>
On Tue, Aug 2, 2011 at 2:45 PM, Shribman, Aidan <aidan.shribman@sap.com> wrote:
>> -----Original Message-----
>> From: Stefan Hajnoczi [mailto:stefanha@gmail.com]
>> Sent: Friday, July 08, 2011 12:07 AM
>> To: Shribman, Aidan
>> Cc: qemu-devel@nongnu.org; Anthony Liguori
>> Subject: Re: [PATCH v2] XBRLE page delta compression for live
>> migration of large memory apps
>>
>>
>> Out of interest, why did ARC not work well as the caching algorithm?
>> Did you try it out and measure its performance?
>>
>
> ARC would be a good candidate for serving as the page cache (storing content previously sent pages) but due to potential legal issues in light of IBM filing for patent on the ARC algorithm on November 2003 (see http://www.varlena.com/GeneralBits/96.php) I presume best if we refrain from using ARC in QEMU until situation is fully cleared.
I see. Thanks for explaining that, I was curious because the paper is
very brief on the details of caching algorithm selection.
Stefan
prev parent reply other threads:[~2011-08-02 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 12:01 [Qemu-devel] [PATCH v2] XBRLE page delta compression for live migration of large memory apps Shribman, Aidan
2011-07-07 8:23 ` Stefan Hajnoczi
2011-08-02 13:45 ` Shribman, Aidan
2011-08-02 18:17 ` Stefan Hajnoczi
2011-07-07 21:07 ` Stefan Hajnoczi
2011-08-02 13:45 ` Shribman, Aidan
2011-08-02 15:53 ` Stefan Hajnoczi [this message]
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=CAJSP0QV6UxAz9e_6o13On2NWWnGb4P7CsFQ0UToPWhVZBaBpuA@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=aidan.shribman@sap.com \
--cc=qemu-devel@nongnu.org \
/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).