On 03.06.2014 16:38, Stefan Hajnoczi wrote:
On Sat, May 31, 2014 at 08:43:07PM +0200, Max Reitz wrote:
For the NBD server to work with dataplane, it needs to correctly access
the exported BDS. It makes the most sense to run both in the same
AioContext, therefore this series implements methods fo
On Sat, May 31, 2014 at 10:24:47PM +0200, Max Reitz wrote:
> On 31.05.2014 20:43, Max Reitz wrote:
> >[snip]
> >
> >However, if bs_aio_detach() is called from a different thread than the
> >old AioContext is running in, we may still have coroutines running for
> >which we should wait before returni
On Sat, May 31, 2014 at 08:43:07PM +0200, Max Reitz wrote:
> For the NBD server to work with dataplane, it needs to correctly access
> the exported BDS. It makes the most sense to run both in the same
> AioContext, therefore this series implements methods for tracking a
> BDS's AioContext and makes
On Sat, May 31, 2014 at 08:43:07PM +0200, Max Reitz wrote:
> For the NBD server to work with dataplane, it needs to correctly access
> the exported BDS. It makes the most sense to run both in the same
> AioContext, therefore this series implements methods for tracking a
> BDS's AioContext and makes
On 31.05.2014 20:43, Max Reitz wrote:
[snip]
However, if bs_aio_detach() is called from a different thread than the
old AioContext is running in, we may still have coroutines running for
which we should wait before returning from bs_aio_detach().
After re-reading Stefan's RFC and the AIO locki
For the NBD server to work with dataplane, it needs to correctly access
the exported BDS. It makes the most sense to run both in the same
AioContext, therefore this series implements methods for tracking a
BDS's AioContext and makes NBD make use of this for keeping the clients
connected to that BDS
