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] Q on shared_mem and event_channel

To: ravi kerur <rkerur@xxxxxxxxx>
Subject: Re: [Xen-devel] Q on shared_mem and event_channel
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Tue, 8 Feb 2011 16:57:41 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-devel-request@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 08 Feb 2011 13:59:12 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTi=AyYMF3xMULLnL73LfDZArdTYYkF9D3p3E26JY@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTi=AyYMF3xMULLnL73LfDZArdTYYkF9D3p3E26JY@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
On Tue, Feb 08, 2011 at 01:34:48PM -0800, ravi kerur wrote:
> Hello,
> 
> I think this might have been discussed numerous times on this mailing-list,
> if there is a relevant post I can refer to please point that to me. What I
> am trying to do is set up a shared memory/event-channels between dom0 and
> domU's via socket calls because I cannot use existing front-end/back-end
> driver mechanism since it relies on devices aka vif, vbd type of device to
> be created and uses xenbus/xenstored for communication between domains.
> Adding support for new device similar to vif/vbd may require xapi changes as
> well which I would like to avoid. Instead write own socket library calls aka
> bind/connect and use them to setup shared memory and event channels between
> domains. I haven't sketched out details yet, but thought of checking if this
> would be feasible.

Like this:
http://www.gossamer-threads.com/lists/xen/devel/197987
?

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

<Prev in Thread] Current Thread [Next in Thread>