From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Fam Zheng" <fam@euphon.net>,
qemu-block@nongnu.org, "Max Reitz" <mreitz@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PATCH 0/7] block/nvme: support nested aio_poll()
Date: Tue, 19 May 2020 18:11:31 +0100 [thread overview]
Message-ID: <20200519171138.201667-1-stefanha@redhat.com> (raw)
This series allows aio_poll() to work from I/O request completion callbacks.
QEMU block drivers are supposed to support this because some code paths rely on
this behavior.
There was no measurable performance difference with nested aio_poll() support.
This patch series also contains cleanups that I made while examining and
benchmarking the code.
Stefan Hajnoczi (7):
block/nvme: poll queues without q->lock
block/nvme: drop tautologous assertion
block/nvme: don't access CQE after moving cq.head
block/nvme: switch to a NVMeRequest freelist
block/nvme: clarify that free_req_queue is protected by q->lock
block/nvme: keep BDRVNVMeState pointer in NVMeQueuePair
block/nvme: support nested aio_poll()
block/nvme.c | 220 ++++++++++++++++++++++++++++++++-------------
block/trace-events | 2 +-
2 files changed, 160 insertions(+), 62 deletions(-)
--
2.25.3
next reply other threads:[~2020-05-19 17:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 17:11 Stefan Hajnoczi [this message]
2020-05-19 17:11 ` [PATCH 1/7] block/nvme: poll queues without q->lock Stefan Hajnoczi
2020-05-25 8:07 ` Sergio Lopez
2020-05-28 15:23 ` Stefan Hajnoczi
2020-05-29 7:49 ` Sergio Lopez
2020-06-17 12:52 ` Stefan Hajnoczi
2020-05-19 17:11 ` [PATCH 2/7] block/nvme: drop tautologous assertion Stefan Hajnoczi
2020-05-25 8:08 ` Sergio Lopez
2020-05-26 12:00 ` Philippe Mathieu-Daudé
2020-05-19 17:11 ` [PATCH 3/7] block/nvme: don't access CQE after moving cq.head Stefan Hajnoczi
2020-05-25 8:12 ` Sergio Lopez
2020-05-26 12:03 ` Philippe Mathieu-Daudé
2020-05-19 17:11 ` [PATCH 4/7] block/nvme: switch to a NVMeRequest freelist Stefan Hajnoczi
2020-05-25 8:10 ` Sergio Lopez
2020-05-19 17:11 ` [PATCH 5/7] block/nvme: clarify that free_req_queue is protected by q->lock Stefan Hajnoczi
2020-05-25 8:13 ` Sergio Lopez
2020-05-26 12:04 ` Philippe Mathieu-Daudé
2020-05-19 17:11 ` [PATCH 6/7] block/nvme: keep BDRVNVMeState pointer in NVMeQueuePair Stefan Hajnoczi
2020-05-25 8:22 ` Sergio Lopez
2020-05-26 14:55 ` Philippe Mathieu-Daudé
2020-05-26 15:20 ` Philippe Mathieu-Daudé
2020-05-28 15:25 ` Stefan Hajnoczi
2020-05-19 17:11 ` [PATCH 7/7] block/nvme: support nested aio_poll() Stefan Hajnoczi
2020-05-25 8:26 ` Sergio Lopez
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=20200519171138.201667-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=philmd@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).