On Sat, Jun 07, 2014 at 09:27:26PM +0200, Max Reitz wrote:
> On 06.06.2014 09:44, Paolo Bonzini wrote:
> >Il 05/06/2014 20:18, Max Reitz ha scritto:
> >>>
> >>>Why is this design cleaner? Because NBD code doesn't have to worry
> >>>about fd handlers. It uses straightforward coroutine send/recv fo
On 06.06.2014 09:44, Paolo Bonzini wrote:
Il 05/06/2014 20:18, Max Reitz ha scritto:
Why is this design cleaner? Because NBD code doesn't have to worry
about fd handlers. It uses straightforward coroutine send/recv for
socket I/O inside nbd_read_req() and nbd_write_resp(). It's easy to
see
Il 05/06/2014 20:18, Max Reitz ha scritto:
Why is this design cleaner? Because NBD code doesn't have to worry
about fd handlers. It uses straightforward coroutine send/recv for
socket I/O inside nbd_read_req() and nbd_write_resp(). It's easy to see
that only one coroutine receives from the so
On 04.06.2014 14:37, Stefan Hajnoczi wrote:
On Sat, May 31, 2014 at 08:43:10PM +0200, Max Reitz wrote:
Instead of using the main loop function qemu_set_fd_handler2(), use the
AIO function in the context of the exported BDS.
Managing fd handlers shouldn't be necessary at the NBD code level. The
On Thu, Jun 05, 2014 at 11:27:49AM +0200, Paolo Bonzini wrote:
> Il 05/06/2014 10:12, Stefan Hajnoczi ha scritto:
> >On Wed, Jun 04, 2014 at 08:02:06PM +0200, Paolo Bonzini wrote:
> >>Il 04/06/2014 14:37, Stefan Hajnoczi ha scritto:
> >>>Why is this design cleaner? Because NBD code doesn't have to
Il 05/06/2014 10:12, Stefan Hajnoczi ha scritto:
On Wed, Jun 04, 2014 at 08:02:06PM +0200, Paolo Bonzini wrote:
Il 04/06/2014 14:37, Stefan Hajnoczi ha scritto:
Why is this design cleaner? Because NBD code doesn't have to worry
about fd handlers. It uses straightforward coroutine send/recv fo
On Wed, Jun 04, 2014 at 08:02:06PM +0200, Paolo Bonzini wrote:
> Il 04/06/2014 14:37, Stefan Hajnoczi ha scritto:
> >Why is this design cleaner? Because NBD code doesn't have to worry
> >about fd handlers. It uses straightforward coroutine send/recv for
> >socket I/O inside nbd_read_req() and nbd
Il 04/06/2014 14:37, Stefan Hajnoczi ha scritto:
Why is this design cleaner? Because NBD code doesn't have to worry
about fd handlers. It uses straightforward coroutine send/recv for
socket I/O inside nbd_read_req() and nbd_write_resp(). It's easy to see
that only one coroutine receives from t
On Sat, May 31, 2014 at 08:43:10PM +0200, Max Reitz wrote:
> Instead of using the main loop function qemu_set_fd_handler2(), use the
> AIO function in the context of the exported BDS.
Managing fd handlers shouldn't be necessary at the NBD code level. The
current NBD code hasn't been fully convert
Instead of using the main loop function qemu_set_fd_handler2(), use the
AIO function in the context of the exported BDS.
Signed-off-by: Max Reitz
---
nbd.c | 21 +++--
1 file changed, 15 insertions(+), 6 deletions(-)
diff --git a/nbd.c b/nbd.c
index 0787cba..803b3d7 100644
--- a
10 matches
Mail list logo
