[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: Kip Macy <kip.macy@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.