From: David Vrabel <david.vrabel@citrix.com>
To: Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Tim Deegan <tim@xen.org>,
xen-devel@lists.xen.org
Subject: Re: [PATCH 0/3] Introduce xensock socket and implement sockback and sockfront drivers
Date: Fri, 8 Aug 2014 13:36:03 +0100 [thread overview]
Message-ID: <53E4C433.6070600@citrix.com> (raw)
In-Reply-To: <1407497529-8585-1-git-send-email-oleksandr.dmytryshyn@globallogic.com>
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.
David
next prev parent reply other threads:[~2014-08-08 12:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 11:32 [PATCH 0/3] Introduce xensock socket and implement sockback and sockfront drivers Oleksandr Dmytryshyn
2014-08-08 11:32 ` [PATCH 1/3] net: introduce new socket support: xensock Oleksandr Dmytryshyn
2014-08-08 11:32 ` [PATCH 2/3] xen-sockback: add support of the xen-sockback driver Oleksandr Dmytryshyn
2014-08-08 11:32 ` [PATCH 3/3] xen-sockfront: add support of the xen-sockfront driver Oleksandr Dmytryshyn
2014-08-08 12:36 ` David Vrabel [this message]
2014-08-08 14:41 ` [PATCH 0/3] Introduce xensock socket and implement sockback and sockfront drivers Stefano Stabellini
2014-08-20 17:58 ` Ian Campbell
2014-08-11 9:40 ` Vitaly V. Ch
2014-08-11 9:50 ` Vitaly V. Ch
2014-08-08 15:27 ` Wei Liu
2014-08-11 9:28 ` Oleksandr Dmytryshyn
2014-08-11 12:58 ` David Vrabel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53E4C433.6070600@citrix.com \
--to=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=oleksandr.dmytryshyn@globallogic.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.