From: Stefano Garzarella <sgarzare@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Hanna Reitz <hreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: [PATCH v2 0/3] linux-aio: allow block devices to limit aio-max-batch
Date: Tue, 26 Oct 2021 18:23:43 +0200 [thread overview]
Message-ID: <20211026162346.253081-1-sgarzare@redhat.com> (raw)
v1: https://lore.kernel.org/qemu-devel/20210923143100.182979-1-sgarzare@redhat.com
v2:
- @aio-max-batch documentation rewrite [Stefan, Kevin]
- added Stefan and Kevin R-b tags
Commit d7ddd0a161 ("linux-aio: limit the batch size using
`aio-max-batch` parameter") added a way to limit the batch size
of Linux AIO backend for the entire AIO context.
The same AIO context can be shared by multiple devices, so
latency-sensitive devices may want to limit the batch size even
more to avoid increasing latency.
This series add the `aio-max-batch` option to the file backend,
and use it in laio_co_submit() and laio_io_unplug() to limit the
Linux AIO batch size more than the limit set by the AIO context.
Stefano Garzarella (3):
file-posix: add `aio-max-batch` option
linux-aio: add `dev_max_batch` parameter to laio_co_submit()
linux-aio: add `dev_max_batch` parameter to laio_io_unplug()
qapi/block-core.json | 7 +++++++
include/block/raw-aio.h | 6 ++++--
block/file-posix.c | 14 ++++++++++++--
block/linux-aio.c | 38 +++++++++++++++++++++++++++-----------
4 files changed, 50 insertions(+), 15 deletions(-)
--
2.31.1
next reply other threads:[~2021-10-26 16:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 16:23 Stefano Garzarella [this message]
2021-10-26 16:23 ` [PATCH v2 1/3] file-posix: add `aio-max-batch` option Stefano Garzarella
2021-10-27 4:28 ` Markus Armbruster
2021-10-27 9:23 ` Stefano Garzarella
2021-10-27 13:06 ` Kevin Wolf
2021-10-27 14:50 ` Stefano Garzarella
2021-11-02 11:52 ` Stefano Garzarella
2021-10-27 9:07 ` Stefan Hajnoczi
2021-10-26 16:23 ` [PATCH v2 2/3] linux-aio: add `dev_max_batch` parameter to laio_co_submit() Stefano Garzarella
2021-10-26 16:23 ` [PATCH v2 3/3] linux-aio: add `dev_max_batch` parameter to laio_io_unplug() Stefano Garzarella
2021-11-02 12:07 ` [PATCH v2 0/3] linux-aio: allow block devices to limit aio-max-batch Kevin Wolf
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=20211026162346.253081-1-sgarzare@redhat.com \
--to=sgarzare@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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 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).