Re: [Xen-devel] [PATCH v6 15/18] xen/pvcalls: implement the ioworker functions

2017-07-05 Thread Stefano Stabellini
On Tue, 4 Jul 2017, Juergen Gross wrote: > On 03/07/17 23:08, Stefano Stabellini wrote: > > We have one ioworker per socket. Each ioworker goes through the list of > > outstanding read/write requests. Once all requests have been dealt with, > > it returns. > > > > We use one atomic counter per soc

Re: [Xen-devel] [PATCH v6 15/18] xen/pvcalls: implement the ioworker functions

2017-07-04 Thread Juergen Gross
On 03/07/17 23:08, Stefano Stabellini wrote: > We have one ioworker per socket. Each ioworker goes through the list of > outstanding read/write requests. Once all requests have been dealt with, > it returns. > > We use one atomic counter per socket for "read" operations and one > for "write" opera

[Xen-devel] [PATCH v6 15/18] xen/pvcalls: implement the ioworker functions

2017-07-03 Thread Stefano Stabellini
We have one ioworker per socket. Each ioworker goes through the list of outstanding read/write requests. Once all requests have been dealt with, it returns. We use one atomic counter per socket for "read" operations and one for "write" operations to keep track of the reads/writes to do. We also u