[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: ravi kerur <rkerur@xxxxxxxxx>
  • Date: Tue, 8 Feb 2011 13:55:48 -0800
  • Delivery-date: Tue, 08 Feb 2011 13:56:22 -0800
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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.


On Tue, Feb 8, 2011 at 1:34 PM, ravi kerur <rkerur@xxxxxxxxx> wrote:

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.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.