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] [PATCH 0/6] PM extension to domU

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH 0/6] PM extension to domU
From: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Date: Wed, 7 Feb 2007 00:01:11 -0500
Delivery-date: Tue, 06 Feb 2007 21:01:39 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <D470B4E54465E3469E2ABBC5AFAC390F9E11DD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <C1EEE280.8FB0%Keir.Fraser@xxxxxxxxxxxx> <D470B4E54465E3469E2ABBC5AFAC390F9E11DD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdJxpGp/qx+TgWOS6iQUGwbfBu5mQAcYarIAAczzZAAAZln5gAAG9xgAAY4JhA=
Thread-topic: [Xen-devel] [PATCH 0/6] PM extension to domU
> So this is the point about definition about driver domains. If we
> consider driver domain as the part of I/O virtualization service
> provider like dom0, minios-style is perfectly right and quick.
> However we have to consider the cases where user just wants
> device passthrough for performance. Actually most requirements
> on the list before driver domain was back to xen3.0, are all related
> to a full guest which doesn't provide backend service to others.
> 
> Then actually we have two scenarios:
>       - Minios-driver domains created automatically to balance I/O
> virtualization, as part of increasing overall xen performance
>       - Full guest with direct device assignment just for performance,
> which is created by user manually

Kevin, Keir,

Are Mini-OS based driver domains possible today? Is there a group
working on this?

Thanks,
Aravindh

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel