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

[Xen-devel] Q on shared_mem and event_channel


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-devel-request@xxxxxxxxxxxxxxxxxxx
  • From: ravi kerur <rkerur@xxxxxxxxx>
  • Date: Tue, 8 Feb 2011 13:34:48 -0800
  • Delivery-date: Tue, 08 Feb 2011 13:35:45 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=bzgePq+zPClmCEeK6+z46+sImiV5G1O27FncPGvT1NWfyFDgC/TmgTESH/Jz6cd+2X +B621+N8Zbpk9gPsTPQr5pmb7ohtijSywrz2YDSd98wrDRMbXMGRgPXA33R65VCHMidB 0BtCJsbsllfFyB9RQWMG05Az5S5RtS411R+80=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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

 


Rackspace

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