From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.2 v3 0/3] nbd: Adapt for dataplane
Date: Tue, 24 Jun 2014 18:34:48 +0200 [thread overview]
Message-ID: <20140624163448.GL3458@noname.redhat.com> (raw)
In-Reply-To: <20140623101301.GA15351@stefanha-thinkpad.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]
Am 23.06.2014 um 12:13 hat Stefan Hajnoczi geschrieben:
> On Fri, Jun 20, 2014 at 09:57:31PM +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 NBD make use of this for keeping the clients
> > connected to that BDS in the same AioContext.
> >
> > This series breaks compilation of NBD on Windows, because
> > aio_set_fd_handler() is not available there yet. It should therefore not
> > be merged until that function is available (which will probably not
> > happen before qemu 2.2).
> >
> >
> > v3:
> > - Patch 1: Drop aio_notify(), because aio_set_fd_handler() will call it
> > anyway [Stefan]
> >
> > v2:
> > - Patch 1: Drop NBDClient::restart_write; checking whether
> > NBDClient::send_coroutine is not NULL suffices [Paolo]
> >
> >
> > git-backport-diff against v2:
> >
> > Key:
> > [----] : patches are identical
> > [####] : number of functional differences between upstream/downstream patch
> > [down] : patch is downstream-only
> > The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
> >
> > 001/3:[0006] [FC] 'nbd: Drop nbd_can_read()'
> > 002/3:[----] [--] 'block: Add AIO context notifiers'
> > 003/3:[----] [--] 'nbd: Follow the BDS' AIO context'
> >
> >
> > Max Reitz (3):
> > nbd: Drop nbd_can_read()
> > block: Add AIO context notifiers
> > nbd: Follow the BDS' AIO context
> >
> > block.c | 56 +++++++++++++++++++++++++
> > include/block/block_int.h | 41 ++++++++++++++++++
> > nbd.c | 103 +++++++++++++++++++++++++++++++++++++---------
> > 3 files changed, 181 insertions(+), 19 deletions(-)
> >
> > --
> > 2.0.0
> >
> >
>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Thanks, applied to the block branch.
Kevin
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-06-24 16:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 19:57 [Qemu-devel] [PATCH for-2.2 v3 0/3] nbd: Adapt for dataplane Max Reitz
2014-06-20 19:57 ` [Qemu-devel] [PATCH for-2.2 v3 1/3] nbd: Drop nbd_can_read() Max Reitz
2014-06-20 19:57 ` [Qemu-devel] [PATCH for-2.2 v3 2/3] block: Add AIO context notifiers Max Reitz
2014-06-20 19:57 ` [Qemu-devel] [PATCH for-2.2 v3 3/3] nbd: Follow the BDS' AIO context Max Reitz
2014-06-23 10:13 ` [Qemu-devel] [PATCH for-2.2 v3 0/3] nbd: Adapt for dataplane Stefan Hajnoczi
2014-06-24 16:34 ` Kevin Wolf [this message]
2014-08-29 9:51 ` Stefan Hajnoczi
2014-08-15 13:08 ` Kevin Wolf
2014-08-15 13:31 ` Max Reitz
2014-08-15 17:15 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140624163448.GL3458@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.