From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCH 0/3] Introduce xensock socket and implement sockback and sockfront drivers Date: Fri, 8 Aug 2014 13:36:03 +0100 Message-ID: <53E4C433.6070600@citrix.com> References: <1407497529-8585-1-git-send-email-oleksandr.dmytryshyn@globallogic.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1407497529-8585-1-git-send-email-oleksandr.dmytryshyn@globallogic.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Oleksandr Dmytryshyn , Ian Campbell , Stefano Stabellini , Tim Deegan , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org 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