| To: | d515a@xxxxxxxxx |
|---|---|
| Subject: | Re: [Xen-devel] CoW memory and Parallax questions. |
| From: | Kip Macy <kip.macy@xxxxxxxxx> |
| Date: | Mon, 3 Oct 2005 12:12:08 -0700 |
| Cc: | xen-devel@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | 2005年10月03日 19:09:58 +0000 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=j/SmipPQ1C9+7HxWKc6HxYjIXC8mJEHe3WbHeBnjGMDksgbG9wTiazfp2kQMJ0LlmLFuPtX/Y200a8ITxF+W8Z+x35L61Ra8STLG4r3rwvyj6iXEmk11NC3ggHsG2xGOZZuD8xTi/M+ltzpp0pShJWHKRo4gNRu24HyTKvWLIRg= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <1128356411.6304.32.camel@xxxxxxxxxxxxxxxxxxxxx> |
| 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> |
| References: | <Pine.LNX.4.61.0509300549450.23433@xxxxxxxxxxxxxxxxxx> <1128356411.6304.32.camel@xxxxxxxxxxxxxxxxxxxxx> |
| Reply-to: | Kip Macy <kip.macy@xxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
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
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: [Xen-devel] 32/64-bit hypercall interface , Nakajima, Jun |
|---|---|
| Next by Date: | Re: [Xen-devel] 32/64-bit hypercall interface - padding , Hollis Blanchard |
| Previous by Thread: | Re: [Xen-devel] CoW memory and Parallax questions. , Jacob Faber Kloster |
| Next by Thread: | Re: [Xen-devel] CoW memory and Parallax questions. , Jacob Gorm Hansen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |