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

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

  • To: Prashanth Radhakrishnan <shanth@xxxxxxxxxxx>
  • From: Andrew Warfield <andrew.warfield@xxxxxxxxxxxx>
  • Date: Sun, 2 Oct 2005 00:04:01 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sat, 01 Oct 2005 23:01:36 +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:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OOSQ6mthavBYykP2BtWJGkfc4t2UwPczBcrdMGJA/a+6bs9BaCDTttHSKmtZdBCViJ6gOE6bDzJbLyAhTAIKrnlBRzsEhR/tKgvnmUgcRbKk739a4KkxYMFw3ongS++Lby0Hh1177TwvnsoQ89MOx3/NOVnHISaJjph++3hmYwY=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> 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) ?

Parallax work is ongoing as well... the block tap source was brought
up to speed with the new tools interface about a month ago and the
parallax sources will follow shortly.  If there is something specific
that you are interested in (or interested in working on ;) ) let me


Xen-devel mailing list



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