Re: [PATCH v7 15/18] xen/pvcalls: implement the ioworker functions

2017-07-06 Thread Juergen Gross
On 05/07/17 23:50, 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"

Re: [PATCH v7 15/18] xen/pvcalls: implement the ioworker functions

2017-07-06 Thread Juergen Gross
On 05/07/17 23:50, 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"

[PATCH v7 15/18] xen/pvcalls: implement the ioworker functions

2017-07-05 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

[PATCH v7 15/18] xen/pvcalls: implement the ioworker functions

2017-07-05 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