Re: [Xen-devel] [PATCH 0/3] Introduce xensock socket and implement sockback and sockfront drivers

["Vitaly V. Ch" <vitaly.v.ch@xxxxxxxxxxxxx>]

On Mon, Aug 11, 2014 at 12:40 PM, Vitaly V. Ch <vitaly.v.ch@xxxxxxxxxxxxx> wrote:

On Fri, Aug 8, 2014 at 3:36 PM, David Vrabel <david.vrabel@xxxxxxxxxx> wrote:

On 08/08/14 12:32, Oleksandr Dmytryshyn wrote:
> Next series of the patches adds new socket support: xensock.
> Those sockets will be used for the xen-sock frontend/backend
> drivers. Those drivers will allow to connect via xensock
> sockets (in this case dom0/domD sockets can be used for the
> server application and domU sockets can be used for the
> client application). Those sockets are similar to the TCP sockets.
> But there are some limitations. Xensock sockets
> ignore an address and can act only as the stream
> sockets. Only one xensock socket can be opened in the frontend
> side and it will be connected with the single xensock socket
> in the backend side (this link is created automatically by
> frontend and backend driver).

You should look at using AF_VSOCK sockets instead.

But in this situation he will need to introduce new protocol in that domain. Do you sure than new protocol is better than new domain? Also does anybody use AF_VSOCK outside vmware?

Also in kernel version where Alexander introduce AF_XENSOCK nothing from AF_VSOCK is present.

With best regards,

Vitaly Chernooky

Â

With best regards,

Vitaly Chernooky

Â

David

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel