Q on shared_mem and event_channel

Q on shared_mem and event_channel

[ravi kerur]

[-- Attachment #1.1: Type: text/plain, Size: 793 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 823 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Q on shared_mem and event_channel

[ravi kerur]

[-- Attachment #1.1: Type: text/plain, Size: 1148 bytes --]

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@gmail.com> 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
>

[-- Attachment #1.2: Type: text/html, Size: 1465 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Q on shared_mem and event_channel

[Konrad Rzeszutek Wilk]

On Tue, Feb 08, 2011 at 01:34:48PM -0800, ravi kerur 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.

Like this:
http://www.gossamer-threads.com/lists/xen/devel/197987
?

Re: Q on shared_mem and event_channel

[ravi kerur]

[-- Attachment #1.1: Type: text/plain, Size: 1579 bytes --]

Thanks Konrad, couple of q's

1. will this work with xenserver 5.6.0(citrix)? reason being, it uses
/dev/xen/gntalloc and /dev/xen/gtndev  and I don't see these devices in
xenserver 5.6.0 dom0 and I don't see similar devices in xenserver 5.6.0

2. I might be able to use this functionality in conjunction with socket
calls, do you see any reason not to do it? Basically in my case I want to
have shared_mem/evt_chn setup either during bootup of dom0/domU's or when my
application is started.

Thanks
-Ravi

On Tue, Feb 8, 2011 at 1:57 PM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:

> On Tue, Feb 08, 2011 at 01:34:48PM -0800, ravi kerur 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.
>
> Like this:
> http://www.gossamer-threads.com/lists/xen/devel/197987
> ?
>

[-- Attachment #1.2: Type: text/html, Size: 2096 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Q on shared_mem and event_channel

[Konrad Rzeszutek Wilk]

On Tue, Feb 08, 2011 at 03:05:31PM -0800, ravi kerur wrote:
> Thanks Konrad, couple of q's
> 
> 1. will this work with xenserver 5.6.0(citrix)? reason being, it uses
> /dev/xen/gntalloc and /dev/xen/gtndev  and I don't see these devices in
> xenserver 5.6.0 dom0 and I don't see similar devices in xenserver 5.6.0

You will have to back-port them to it.
> 
> 2. I might be able to use this functionality in conjunction with socket
> calls, do you see any reason not to do it? Basically in my case I want to
> have shared_mem/evt_chn setup either during bootup of dom0/domU's or when my
> application is started.

Well, that requires much more than the patches I mentioned. I think Citrix
might have some off-the-shelf code that does it. Ask on the Xapi mailing list.

Re: Q on shared_mem and event_channel

[ravi kerur]

[-- Attachment #1.1: Type: text/plain, Size: 1359 bytes --]

Hi Konrad,

xapi mailing list response time is pretty slow(I had experienced it before),
haven't heard from xapi mailing list for my Q yet. If i go to Citrix support
it takes at least a week to get a response.

I am not quite sure whom to followup with. Any inputs appreciated.

Thanks
-Ravi

On Tue, Feb 8, 2011 at 4:07 PM, ravi kerur <rkerur@gmail.com> wrote:

> Thanks Konrad, is xapi mailing list xen-api@lists.xensource.com ?
>
>
> On Tue, Feb 8, 2011 at 3:12 PM, Konrad Rzeszutek Wilk <
> konrad.wilk@oracle.com> wrote:
>
>> On Tue, Feb 08, 2011 at 03:05:31PM -0800, ravi kerur wrote:
>> > Thanks Konrad, couple of q's
>> >
>> > 1. will this work with xenserver 5.6.0(citrix)? reason being, it uses
>> > /dev/xen/gntalloc and /dev/xen/gtndev  and I don't see these devices in
>> > xenserver 5.6.0 dom0 and I don't see similar devices in xenserver 5.6.0
>>
>> You will have to back-port them to it.
>> >
>> > 2. I might be able to use this functionality in conjunction with socket
>> > calls, do you see any reason not to do it? Basically in my case I want
>> to
>> > have shared_mem/evt_chn setup either during bootup of dom0/domU's or
>> when my
>> > application is started.
>>
>> Well, that requires much more than the patches I mentioned. I think Citrix
>> might have some off-the-shelf code that does it. Ask on the Xapi mailing
>> list.
>>
>>
>>
>

[-- Attachment #1.2: Type: text/html, Size: 2118 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel