From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Hanna Reitz <hreitz@redhat.com>,
qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PATCH 0/2] block-backend: process I/O in the current AioContext
Date: Tue, 15 Aug 2023 12:05:19 -0400 [thread overview]
Message-ID: <20230815160521.3357063-1-stefanha@redhat.com> (raw)
Switch blk_aio_*() APIs over to multi-queue by using
qemu_get_current_aio_context() instead of blk_get_aio_context(). This change
will allow devices to process I/O in multiple IOThreads in the future.
Stefan Hajnoczi (2):
block-backend: process I/O in the current AioContext
block-backend: process zoned requests in the current AioContext
block/block-backend.c | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
--
2.41.0
next reply other threads:[~2023-08-15 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 16:05 Stefan Hajnoczi [this message]
2023-08-15 16:05 ` [PATCH 1/2] block-backend: process I/O in the current AioContext Stefan Hajnoczi
2023-08-15 16:05 ` [PATCH 2/2] block-backend: process zoned requests " Stefan Hajnoczi
2023-08-18 15:24 ` [PATCH 0/2] block-backend: process I/O " Kevin Wolf
2023-08-21 15:17 ` 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=20230815160521.3357063-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--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).