Re: [Xen-devel] [DOC v1] Xen transport for 9pfs

2016-12-02 Thread Stefano Stabellini
On Fri, 2 Dec 2016, Dario Faggioli wrote: > On Thu, 2016-12-01 at 15:14 -0800, Stefano Stabellini wrote: > > On Thu, 1 Dec 2016, Dario Faggioli wrote: > > > > > > On Tue, 2016-11-29 at 15:34 -0800, Stefano Stabellini wrote: > > > >  > > > > ring-ref- (ring-ref-0, ring-ref-1, etc) > > > > > >

Re: [Xen-devel] [DOC v1] Xen transport for 9pfs

2016-12-02 Thread Stefano Stabellini
On Fri, 2 Dec 2016, David Vrabel wrote: > On 02/12/16 00:29, Stefano Stabellini wrote: > > On Wed, 30 Nov 2016, David Vrabel wrote: > >> On 29/11/16 23:34, Stefano Stabellini wrote: > >>> > >>> The producer (the backend for **in**, the frontend for **out**) writes to > >>> the > >>> array in the

Re: [Xen-devel] [DOC v1] Xen transport for 9pfs

2016-12-02 Thread Andrew Cooper
On 02/12/16 00:29, Stefano Stabellini wrote: > On Wed, 30 Nov 2016, David Vrabel wrote: >> On 29/11/16 23:34, Stefano Stabellini wrote: >>> The producer (the backend for **in**, the frontend for **out**) writes to >>> the >>> array in the following way: >>> >> - read memory barrier >>> - read

Re: [Xen-devel] [DOC v1] Xen transport for 9pfs

2016-12-02 Thread David Vrabel
On 02/12/16 00:29, Stefano Stabellini wrote: > On Wed, 30 Nov 2016, David Vrabel wrote: >> On 29/11/16 23:34, Stefano Stabellini wrote: >>> >>> The producer (the backend for **in**, the frontend for **out**) writes to >>> the >>> array in the following way: >>> >> - read memory barrier >>> - read

Re: [Xen-devel] [DOC v1] Xen transport for 9pfs

2016-12-02 Thread Dario Faggioli
On Thu, 2016-12-01 at 15:14 -0800, Stefano Stabellini wrote: > On Thu, 1 Dec 2016, Dario Faggioli wrote: > > > > On Tue, 2016-11-29 at 15:34 -0800, Stefano Stabellini wrote: > > >  > > > ring-ref- (ring-ref-0, ring-ref-1, etc) > > > > > blkif uses ring-ref%u, rather than ring-ref-%u (i.e.,

Re: [Xen-devel] [DOC v1] Xen transport for 9pfs

2016-12-01 Thread Stefano Stabellini
On Wed, 30 Nov 2016, David Vrabel wrote: > On 29/11/16 23:34, Stefano Stabellini wrote: > > > > The producer (the backend for **in**, the frontend for **out**) writes to > > the > > array in the following way: > > > - read memory barrier > > - read *cons*, *prod* from shared memory > > - write

Re: [Xen-devel] [DOC v1] Xen transport for 9pfs

2016-12-01 Thread Stefano Stabellini
On Thu, 1 Dec 2016, Dario Faggioli wrote: > On Tue, 2016-11-29 at 15:34 -0800, Stefano Stabellini wrote: > > ### Frontend XenBus Nodes > > > > num-rings > >  Values:  > > > >  Number of rings. It needs to be lower or equal to max-rings. > > > > port-

Re: [Xen-devel] [DOC v1] Xen transport for 9pfs

2016-12-01 Thread Dario Faggioli
On Tue, 2016-11-29 at 15:34 -0800, Stefano Stabellini wrote: > ### Frontend XenBus Nodes > > num-rings >  Values:  > >  Number of rings. It needs to be lower or equal to max-rings. > > port- (port-0, port-1, etc) >  Values:  > >   

Re: [Xen-devel] [DOC v1] Xen transport for 9pfs

2016-11-30 Thread David Vrabel
On 29/11/16 23:34, Stefano Stabellini wrote: > > The producer (the backend for **in**, the frontend for **out**) writes to the > array in the following way: > - read memory barrier > - read *cons*, *prod* from shared memory > - write to array at position *prod* up to *cons*, wrapping around the

[Xen-devel] [DOC v1] Xen transport for 9pfs

2016-11-29 Thread Stefano Stabellini
# Xen transport for 9pfs version 1 ## Background 9pfs is a network filesystem protocol developed for Plan 9. 9pfs is very simple and describes a series of commands and responses. It is completely independent from the communication channels, in fact many clients and servers support multiple