Re: [Xen-devel] [DRAFT 1] XenSock protocol design document

2016-07-13 Thread Stefano Stabellini
On Mon, 11 Jul 2016, Joao Martins wrote: > On 07/08/2016 12:23 PM, Stefano Stabellini wrote: > > Hi all, > > > Hey! > > [...] > > > > > ## Design > > > > ### Xenstore > > > > The frontend and the backend connect to each other exchanging information > > via > > xenstore. The toolstack creates

Re: [Xen-devel] [DRAFT 1] XenSock protocol design document

2016-07-12 Thread Stefano Stabellini
On Mon, 11 Jul 2016, Paul Durrant wrote: > > -Original Message- > [snip] > > > > # XenSocks Protocol v1 > > > > ## Rationale > > > > XenSocks is a paravirtualized protocol for the POSIX socket API. > > > > The purpose of XenSocks is to allow the implementation of a specific set > > of P

Re: [Xen-devel] [DRAFT 1] XenSock protocol design document

2016-07-11 Thread Joao Martins
On 07/08/2016 12:23 PM, Stefano Stabellini wrote: > Hi all, > Hey! [...] > > ## Design > > ### Xenstore > > The frontend and the backend connect to each other exchanging information via > xenstore. The toolstack creates front and back nodes with state > XenbusStateInitialising. There can only

Re: [Xen-devel] [DRAFT 1] XenSock protocol design document

2016-07-11 Thread Paul Durrant
> -Original Message- [snip] > > # XenSocks Protocol v1 > > ## Rationale > > XenSocks is a paravirtualized protocol for the POSIX socket API. > > The purpose of XenSocks is to allow the implementation of a specific set > of POSIX calls to be done in a domain other than your own. It allow

Re: [Xen-devel] [DRAFT 1] XenSock protocol design document

2016-07-11 Thread Stefano Stabellini
On Fri, 8 Jul 2016, David Vrabel wrote: > On 08/07/16 12:23, Stefano Stabellini wrote: > > > > XenSocks provides the following benefits: > > * guest networking works out of the box with VPNs, wireless networks and > > any other complex configurations on the host > > Only in the trivial case whe

Re: [Xen-devel] [DRAFT 1] XenSock protocol design document

2016-07-08 Thread Stefano Stabellini
On Fri, 8 Jul 2016, David Vrabel wrote: > On 08/07/16 17:52, Stefano Stabellini wrote: > > > >> c) My belief that most of the advantages of this proposal can be > >> achieved with smarts in the backend. > > > > By backend do you mean netfront/netback? If so, I have already pointed > > out why tha

Re: [Xen-devel] [DRAFT 1] XenSock protocol design document

2016-07-08 Thread David Vrabel
On 08/07/16 17:52, Stefano Stabellini wrote: > >> c) My belief that most of the advantages of this proposal can be >> achieved with smarts in the backend. > > By backend do you mean netfront/netback? If so, I have already pointed > out why that is not the case in previous emails as well as in thi

Re: [Xen-devel] [DRAFT 1] XenSock protocol design document

2016-07-08 Thread David Vrabel
On 08/07/16 12:23, Stefano Stabellini wrote: > > XenSocks provides the following benefits: > * guest networking works out of the box with VPNs, wireless networks and > any other complex configurations on the host Only in the trivial case where the host only has one external network. Otherwise,

Re: [Xen-devel] [DRAFT 1] XenSock protocol design document

2016-07-08 Thread Stefano Stabellini
On Fri, 8 Jul 2016, David Vrabel wrote: > On 08/07/16 15:16, Stefano Stabellini wrote: > > > > http://pubs.opengroup.org/onlinepubs/7908799/xns/connect.html > > Are you really guaranteeing full POSIX semantics for all these calls? > And not say, POSIX-like except where Linux decides to differ bec

Re: [Xen-devel] [DRAFT 1] XenSock protocol design document

2016-07-08 Thread David Vrabel
On 08/07/16 15:16, Stefano Stabellini wrote: > > http://pubs.opengroup.org/onlinepubs/7908799/xns/connect.html Are you really guaranteeing full POSIX semantics for all these calls? And not say, POSIX-like except where Linux decides to differ because POSIX is dumb? How is the guest (which expects

Re: [Xen-devel] [DRAFT 1] XenSock protocol design document

2016-07-08 Thread Juergen Gross
On 08/07/16 16:16, Stefano Stabellini wrote: > Hi Juergen, > > many thanks for the fast and very useful review! > > > On Fri, 8 Jul 2016, Juergen Gross wrote: >> On 08/07/16 13:23, Stefano Stabellini wrote: >>> #define XENSOCK_DATARING_ORDER 6 >>> #define XENSOCK_DATARING_PAGES (1 << XEN

Re: [Xen-devel] [DRAFT 1] XenSock protocol design document

2016-07-08 Thread Stefano Stabellini
Hi Juergen, many thanks for the fast and very useful review! On Fri, 8 Jul 2016, Juergen Gross wrote: > On 08/07/16 13:23, Stefano Stabellini wrote: > > Hi all, > > > > as promised, this is the design document for the XenSock protocol I > > mentioned here: > > > > http://marc.info/?l=xen-devel

Re: [Xen-devel] [DRAFT 1] XenSock protocol design document

2016-07-08 Thread Juergen Gross
On 08/07/16 13:23, Stefano Stabellini wrote: > Hi all, > > as promised, this is the design document for the XenSock protocol I > mentioned here: > > http://marc.info/?l=xen-devel&m=146520572428581 > > It is still in its early days but should give you a good idea of how it > looks like and how it

[Xen-devel] [DRAFT 1] XenSock protocol design document

2016-07-08 Thread Stefano Stabellini
Hi all, as promised, this is the design document for the XenSock protocol I mentioned here: http://marc.info/?l=xen-devel&m=146520572428581 It is still in its early days but should give you a good idea of how it looks like and how it is supposed to work. Let me know if you find gaps in the docum