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/
Home Products Support Community News


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

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] Q on shared memory and evt-channel
From: ravi kerur <rkerur@xxxxxxxxx>
Date: Tue, 8 Feb 2011 16:06:27 -0800
Delivery-date: Tue, 08 Feb 2011 20:12:25 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=r8r912CvaBsVDWjCrL8IRHy3b4oDhtxPjIiKjQY+W0U=; b=bt6ct06pU/+bOrlY+uKP1YB9PMaWrWLsP95545SO79U4e73hm9i4cE1NtBRYSf++Ff cryzJO++PDKtdxVuudcjBNmZWgStrY6PaQfYzL05f+MGOS72Va+8DWRSWNzZh0vQN0Hb o+ALV6uWt/iyKXFzxjN3U/ICy7bOQeKZVrZ8w=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx

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.


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.

xen-api mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-API] Q on shared memory and evt-channel, ravi kerur <=