From: Stefan Hajnoczi <stefanha@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.2 v3 0/3] nbd: Adapt for dataplane
Date: Fri, 15 Aug 2014 18:15:34 +0100 [thread overview]
Message-ID: <20140815171534.GA14646@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <53EE0BC4.50705@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2145 bytes --]
On Fri, Aug 15, 2014 at 03:31:48PM +0200, Max Reitz wrote:
> On 15.08.2014 15:08, Kevin Wolf wrote:
> >Am 20.06.2014 um 21:57 hat Max Reitz geschrieben:
> >>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]
> >Dropped from the block branch because it breaks the win32 build:
> >
> >nbd.c: In function 'nbd_set_handlers':
> >nbd.c:1323:9: warning: implicit declaration of function 'aio_set_fd_handler' [-Wimplicit-function-declaration]
> > aio_set_fd_handler(client->exp->ctx, client->sock,
> > ^
> >nbd.c:1323:9: warning: nested extern declaration of 'aio_set_fd_handler' [-Wnested-externs]
> >
> >And the resulting undefined references during linking.
>
> As stated by the cover letter you're replying to. :-) Sorry I did not pay
> enough attention when you merged this series to your tree, I should have
> explicitly warned you.
>
> Right, we need to implement aio_set_fd_handler() for the win32/win64 build
> before this series can really be merged. Paolo said this could be done until
> 2.2, so that's why this series is marked "for-2.2". I guess I'll have to
> keep a close look on qemu-devel whenever someone posts something resembling
> aio_set_fd_handler() for win32/win64.
Paolo's "[PATCH 00/25] AioContext & threadpool" is what we need.
Waiting for him to respin.
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2014-08-15 17:15 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
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 [this message]
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=20140815171534.GA14646@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).