Re: [Xen-devel] CoW memory and Parallax questions.

[Kip Macy <kip.macy@xxxxxxxxx>]

They aren't mutually exclusive, but a content-based approach, although
more flexible, seems like it would inevitably be much heavier weight. 
What is your solution targeted towards?

 -Kip

On 10/3/05, Jacob Faber Kloster <jk@xxxxxxxxx> wrote:

Now when the topic of Copy-on-Write memory sharing is up. It might be in
place to tell that we (a group of tree master students), will be doing
work on content based Copy-on-Write memory sharing. Similar to what is
implemented in VMWare's ESX server. See
http://www.waldspurger.org/carl/papers/esx-mem-osdi02.pdf

We have contacted Michael Vrable about his approach, and it is likely
that our code will be an extension of his.

Best regards
Jacob Faber Kloster (group email d515a.cs.aau.dk)

On Fri, 2005-09-30 at 05:52 -0600, Prashanth Radhakrishnan wrote:
> Does Xen-unstable do Copy-on-Write sharing of memory between VMs ?
> If not, is someone working on it ?
> I last see a mention about Micheal Vrable working on it back in Oct 2004
> - http://lists.xensource.com/archives/html/xen-devel/2004-10/msg00470.html.
>
> Also curious to find out the status on Parallax; is someone working on
> adding persistent caching, remote block access and other features as
> described in the parallax paper (it seems that the current implementation
> has remote access or local access) ?
>
> thanks,
> prashanth
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel