[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] CoW memory and Parallax questions.
- To: d515a@xxxxxxxxx
- From: Kip Macy <kip.macy@xxxxxxxxx>
- Date: Tue, 4 Oct 2005 10:34:37 -0700
- Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Jacob Gorm Hansen <jacobg@xxxxxxx>
- Delivery-date: Tue, 04 Oct 2005 17:32:11 +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=Ovvn853RCJhbho/fgPel89flcokN6OSm2zKyclrozbaL9xHcWI7sHepzB6gnBMcMXcr3pfVpnO6FpsvswPXDJ79cbVQbINxlf1Vu1tsVloy4hOdryagk7GguMKPaLryUVLtQKa2z/eT59UljOGp7W6UE3ty3wyFZMD9xMZWLk74=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
I don't think HV level privilege is necessary. Take a look at the
mergemem work. A service running in the background in DOM0 is a
potentially viable approach.
-Kip
On 10/4/05, Jacob Faber Kloster <jk@xxxxxxxxx> wrote:
That certainly sounds like an interesting approach. Our immediate
approach was something along the lines of making a separate service, on
the hypervisor level of privilege, with complete overview and control of
the memory. Doing the content based sharing scheme will, as you also
noted, open up the possibility of overcommitment of memory. Some kind of
scheduling will be needed to handle this. One solution could be to
suspend a VM to disk or introduce a swapping..
But at this point in time we are not focusing on any specific solution,
we are just investigating whether it is possible and feasible to share
memory.
Best regards
Jacob Faber Kloster (group email d515a@xxxxxxxxx)
On Tue, 2005-10-04 at 10:53 +0200, Jacob Gorm Hansen wrote:
> My take on that would be to introduce read-only pages and a context
> index (tree or hashtable) in Xen, and then handle the CoW part in the
> guest OSes. That removes the need for any policy on how to handle
> overcommits in Xen or Dom0, in the case where all domUs decide to fill
> up their pages with random data.
>
> Jacob
_______________________________________________
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
|
