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

[Xen-API] Q on shared memory and evt-channel


  • To: xen-api@xxxxxxxxxxxxxxxxxxx
  • From: ravi kerur <rkerur@xxxxxxxxx>
  • Date: Tue, 8 Feb 2011 16:06:27 -0800
  • Delivery-date: Tue, 08 Feb 2011 20:12:25 -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=RjwAOMCo4e7l7Lzwvm37v62z8NluNcDj9O41SQc+zje9Uoo2eOGNOX7kfO4b7uhnB2 a93gwyCxkoCwi0AodIZsiEo10e8nMDL0dxDxyC26obE7JlcDCXfkDd+OBkMhapPV/sfP SQHZkVZSRzy9DYBwfUCa1iQwTyldp/UHGFKlM=
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>

Hi,

I am trying to set up a shared memory/event-channels between dom0 and domU's via socket calls. I do not want to use existing front-end/back-end driver mechanism as 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 toolstack changes as well which I would like to avoid. Instead

1. write own socket library calls aka bind/connect and use them to setup shared memory and event channels between domains. I will have client and server side of application, server side running on dom0 and client side on domU's.

or

2. write a kernel module(aka driver) and create devices under /dev/<some_device_name> in both dom0 and domU's and use these device to setup shared mem/evt_chnl.

 I haven't sketched out details yet, but thought of checking if this would be feasible.

Thanks
-Ravi
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

 


Rackspace

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