WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] CoW memory and Parallax questions.

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] CoW memory and Parallax questions.
From: Prashanth Radhakrishnan <shanth@xxxxxxxxxxx>
Date: Fri, 30 Sep 2005 05:52:20 -0600 (MDT)
Delivery-date: Sat, 01 Oct 2005 12:02:35 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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