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] simple backend, frontend

To: Deepak Manohar <mjdeepak@xxxxxxxxx>
Subject: Re: [Xen-devel] simple backend, frontend
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 12 Nov 2004 08:22:14 +0000
Cc: andrew.warfield@xxxxxxxxxxxx, mark.williamson@xxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 12 Nov 2004 08:55:33 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Thu, 11 Nov 2004 14:21:01 EST." <fdef3c24041111112178c14610@xxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
>  Now if I need to add another custom backend using the same method as
> the netif or blkif backends dont I have to modify Xend as well?
> Is there a simpler way of establishing event channels between domains
> by directly accessing the API in xen/common/event_channel.c
>  Some assumptions that Im making - the frontend will be started only
> after the backend is running. Im primarily going to be using this
> frontend/backend for transferring large data between a user domain and
> the control domain.  So I will have to establish shared mem pages as
> well.

To set up an event channel and shared memory between two domains you
need some out-of-band communication, which may or may not be xend.
Instead the communication could be done via an interdomain IP network,
for example. However you arrange it, each domain probably needs to
know the domid of the other guy. Also both ends need to know the
address of the page they are to share, and the remote port for teh
shared event channel.

 -- Keir

This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
Xen-devel mailing list