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

[Xen-devel] Re: Q on shared_mem and event_channel

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: Q on shared_mem and event_channel
From: ravi kerur <rkerur@xxxxxxxxx>
Date: Tue, 8 Feb 2011 13:55:48 -0800
Delivery-date: Tue, 08 Feb 2011 13:56:22 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=mPAPb4C2E8VBrUfzId+04tKUWHO5qK96LDZHb4ZX2YA=; b=cVAWdGz5tZdVZnzjsquC9nISUpIaf1jwLJvxfOvY/6kd1/C1nymoBuckQ08V4Ncizz d3QhMYM3NrzwvB4gsjpcFcGR/fhL0MT8hPi/7R0VdyiKRrdzjwFhpaj5y+TcIOkkhnNQ Nrw40IPEvi1ewZyV2U9VWii1a31QHZ+PkfTWc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=rWJu4x95QTpHg2sRJiQAku7eXwfFx4V4g7Q22lcm9XTtBevWZu7jC/293BSj6D50vV g/lWm40vhc09Zd7sHzGxPeSHnY5a8Ptfkno6QxFft1EvKyyJ+gfq+zL1V8xmKRYC5WDL cYvF3h8i7Ydtdzkux3WZ6G1LhqS3DfrQyUPUo=
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

Forgot to mention an additional option. In addition to sockets, I was thinking to use block-devices i.e create /dev/<block-device> in both dom0 and domU's and use these to communicate between domains...

Your inputs will be highly appreciated.

-Ravi


On Tue, Feb 8, 2011 at 1:34 PM, ravi kerur <rkerur@xxxxxxxxx> 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.

Thanks
-Ravi

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>