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

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

To: Kip Macy <kip.macy@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] CoW memory and Parallax questions.
From: Jacob Gorm Hansen <jacobg@xxxxxxx>
Date: Tue, 4 Oct 2005 10:53:35 +0200
Delivery-date: Tue, 04 Oct 2005 08:51:08 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=crO3dIvPm7Rkxii4DL576hOg9SPURpXUR0wkBoY49OjUH91931UcFXePoXwCFh4L82Q1s3tI/lDUMusfWXT9pyfk3xpFdm8v93MHHbFWRGCn3C9YkeUa5LUJTZE+OV+NotvfXp9X+FYsrSKXTLJSaLLIJ3GjZybPV3D3HjHtExY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <b1fa29170510031212x1609935etaa812e8d8481673d@xxxxxxxxxxxxxx>
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> <b1fa29170510031212x1609935etaa812e8d8481673d@xxxxxxxxxxxxxx>
Reply-to: Jacob Gorm Hansen <jacobg@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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