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/

Home

xen-devel

[Top] [All Lists]

Re: [Fwd: Re: [Xen-devel] [PATCH] skeleton frontend/backend examples and

from [Mark Williamson]

[Permanent Link][Original]

To:	xen-devel@xxxxxxxxxxxxxxxxxxx
Subject:	Re: [Fwd: Re: [Xen-devel] [PATCH] skeleton frontend/backend examples and a deadlock]
From:	Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date:	Fri, 4 Nov 2005 17:15:43 +0000
Cc:	harry <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Delivery-date:	Fri, 04 Nov 2005 17:17:05 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<1131123986.3019.7.camel@xxxxxxxxxxxxxxxxxxxxx>
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:	<1131123986.3019.7.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	KMail/1.8.3

Another question:

XenIDC is designed to handle indirection over the network, etc, right?  Would 
it be possible to make the indirection transparent to the guest by 
implementing it in the backend?  Or would that be the job of the frontend?

It certainly seems cleaner to me to make this as transparent to the guest as 
possible - also reduces guest complexity.

Cheers,
Mark

On Friday 04 November 2005 17:06, harry wrote:

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

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Fwd: Re: [Xen-devel] [PATCH] skeleton frontend/backend examples and a deadlock], harry Re: [Fwd: Re: [Xen-devel] [PATCH] skeleton frontend/backend examples and a deadlock], Mark Williamson <= Re: [Fwd: Re: [Xen-devel] [PATCH] skeleton frontend/backend examples and a deadlock], harry

Previous by Date:	[Xen-devel] TSC and Power Management Events on AMD Processors, Brunner, Richard
Next by Date:	[Xen-devel] Remaining ia64 differences in xen driver code, Magenheimer, Dan (HP Labs Fort Collins)
Previous by Thread:	[Fwd: Re: [Xen-devel] [PATCH] skeleton frontend/backend examples and a deadlock], harry
Next by Thread:	Re: [Fwd: Re: [Xen-devel] [PATCH] skeleton frontend/backend examples and a deadlock], harry
Indexes:	[Date] [Thread] [Top] [All Lists]

This site is hosted by Citrix