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/
Home Products Support Community News


Re: [Xen-devel] Re: Fine-grained proxy resource charging

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Re: Fine-grained proxy resource charging
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Wed, 24 Aug 2005 18:13:26 +0100
Cc: jlg@xxxxxxxxxx, Lucy Cherkasova <lucy@xxxxxxxxxxxxxxxx>
Delivery-date: Wed, 24 Aug 2005 17:13:30 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200508241635.JAA12565@xxxxxxxxxxxxxxxx>
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: <200508241635.JAA12565@xxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8
> Yes, I would join in asking the same question: how to get a working
> configuration for multiple driver domains each hosting a single device
> driver?

You can only really have one domain running the actual driver.  The best 
strategy would therefore be to keep as much IO processing as possible in 
other domains (preferably in the guests themselves).

With user-accessible hardware (e.g. Infiniband), unprivileged guests will be 
able to access their hardware directly using their own CPU time (and get 
better performance in the process).  Of course Infiniband is rather expensive 
so this won't be the most common way of doing stuff for some time (if at 


Xen-devel mailing list