From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Leonardo Bras" <leobras@redhat.com>,
eblake@redhat.com, "Daniel P. Berrangé" <berrange@redhat.com>,
farosas@suse.de, kwolf@redhat.com, "Peter Xu" <peterx@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Vladimir Sementsov-Ogievskiy" <vsementsov@yandex-team.ru>,
"Juan Quintela" <quintela@redhat.com>,
qemu-block@nongnu.org, "Coiby Xu" <Coiby.Xu@gmail.com>,
"Fam Zheng" <fam@euphon.net>, "Hanna Reitz" <hreitz@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: [PATCH v2 0/4] io: follow coroutine AioContext in qio_channel_yield()
Date: Tue, 29 Aug 2023 12:06:18 -0400 [thread overview]
Message-ID: <20230829160623.277411-1-stefanha@redhat.com> (raw)
v2:
- Add Patch 1 & 2 to remove unused NBD aio_context arguments and dead code [Fabiano]
- Remove attach/detach prototypes from "io/channel.h" [Daniel]
- Add utility function to set fd handlers [Daniel]
The ongoing QEMU multi-queue block layer effort makes it possible for multiple
threads to process I/O in parallel. The nbd block driver is not compatible with
the multi-queue block layer yet because QIOChannel cannot be used easily from
coroutines running in multiple threads. This series changes the QIOChannel API
to make that possible.
Stefan Hajnoczi (4):
nbd: drop unused nbd_receive_negotiate() aio_context argument
nbd: drop unused nbd_start_negotiate() aio_context argument
io: check there are no qio_channel_yield() coroutines during
->finalize()
io: follow coroutine AioContext in qio_channel_yield()
include/block/nbd.h | 3 +-
include/io/channel-util.h | 23 ++++++
include/io/channel.h | 69 ++++++++---------
include/qemu/vhost-user-server.h | 1 +
block/nbd.c | 11 +--
io/channel-command.c | 10 ++-
io/channel-file.c | 9 ++-
io/channel-null.c | 3 +-
io/channel-socket.c | 9 ++-
io/channel-tls.c | 6 +-
io/channel-util.c | 24 ++++++
io/channel.c | 124 ++++++++++++++++++++++---------
migration/channel-block.c | 3 +-
nbd/client-connection.c | 3 +-
nbd/client.c | 14 +---
nbd/server.c | 14 +---
qemu-nbd.c | 4 +-
scsi/qemu-pr-helper.c | 4 +-
util/vhost-user-server.c | 27 +++++--
19 files changed, 228 insertions(+), 133 deletions(-)
--
2.41.0
next reply other threads:[~2023-08-29 16:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 16:06 Stefan Hajnoczi [this message]
2023-08-29 16:06 ` [PATCH v2 1/4] nbd: drop unused nbd_receive_negotiate() aio_context argument Stefan Hajnoczi
2023-08-29 18:30 ` Eric Blake
2023-08-30 9:40 ` Philippe Mathieu-Daudé
2023-08-29 16:06 ` [PATCH v2 2/4] nbd: drop unused nbd_start_negotiate() " Stefan Hajnoczi
2023-08-29 18:32 ` Eric Blake
2023-08-30 9:40 ` Philippe Mathieu-Daudé
2023-08-29 16:06 ` [PATCH v2 3/4] io: check there are no qio_channel_yield() coroutines during ->finalize() Stefan Hajnoczi
2023-08-29 16:06 ` [PATCH v2 4/4] io: follow coroutine AioContext in qio_channel_yield() Stefan Hajnoczi
2023-08-29 19:32 ` Eric Blake
2023-08-29 20:29 ` Stefan Hajnoczi
2023-08-30 7:54 ` Daniel P. Berrangé
2023-08-31 13:30 ` Eric Blake
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=20230829160623.277411-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=Coiby.Xu@gmail.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=farosas@suse.de \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=leobras@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=vsementsov@yandex-team.ru \
/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).