From: Aarushi Mehta <mehta.aaru20@gmail.com>
To: qemu-devel@nongnu.org
Cc: saket.sinha89@gmail.com, Julia Suvorova <jusual@mail.ru>,
qemu-block@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Aarushi Mehta <mehta.aaru20@gmail.com>
Subject: [Qemu-devel] [RFC PATCH 0/9] Add support for io_uring
Date: Wed, 22 May 2019 05:22:06 +0530 [thread overview]
Message-ID: <20190521235215.31341-1-mehta.aaru20@gmail.com> (raw)
This patch series adds supports for the newly developed io_uring Linux AIO interface. Testing it requires a host kernel with it and the liburing library. Use the option -drive aio=io_uring to enable it.
Aarushi Mehta (9):
qapi/block-core: add option for io_uring
block/block: add BDRV flag for io_uring
include/block: declare interfaces for io_uring
stubs: add aio interface stubs for io_uring
util/asyn: add aio interfaces for io_uring
block/io_uring: implements interfaces for io_uring
blockdev: accept io_uring as option
block/file-posix: extends to use with io_uring
configure: permits use of io_uring with probe
block/Makefile.objs | 2 +
block/file-posix.c | 63 ++++++-
block/io_uring.c | 385 ++++++++++++++++++++++++++++++++++++++++
blockdev.c | 4 +-
configure | 27 +++
include/block/aio.h | 16 +-
include/block/block.h | 1 +
include/block/raw-aio.h | 15 ++
qapi/block-core.json | 3 +-
stubs/Makefile.objs | 1 +
stubs/io_uring.c | 32 ++++
util/async.c | 32 ++++
12 files changed, 573 insertions(+), 8 deletions(-)
create mode 100644 block/io_uring.c
create mode 100644 stubs/io_uring.c
--
2.17.1
next reply other threads:[~2019-05-22 0:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 23:52 Aarushi Mehta [this message]
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 1/9] qapi/block-core: add option for io_uring Aarushi Mehta
2019-05-22 0:39 ` Eric Blake
2019-05-22 0:51 ` Aarushi Mehta
2019-05-22 1:01 ` Eric Blake
2019-05-22 9:16 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2019-05-22 13:07 ` [Qemu-devel] " Stefan Hajnoczi
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 2/9] block/block: add BDRV flag " Aarushi Mehta
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 3/9] include/block: declare interfaces " Aarushi Mehta
2019-05-22 13:09 ` Stefan Hajnoczi
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 4/9] stubs: add aio interface stubs " Aarushi Mehta
2019-05-22 13:10 ` Stefan Hajnoczi
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 5/9] util/asyn: add aio interfaces " Aarushi Mehta
2019-05-22 13:16 ` Stefan Hajnoczi
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 6/9] block/io_uring: implements " Aarushi Mehta
2019-05-22 15:43 ` Stefan Hajnoczi
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 7/9] blockdev: accept io_uring as option Aarushi Mehta
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 8/9] block/file-posix: extends to use with io_uring Aarushi Mehta
2019-05-22 15:45 ` Stefan Hajnoczi
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 9/9] configure: permits use of io_uring with probe Aarushi Mehta
2019-05-22 0:09 ` [Qemu-devel] [RFC PATCH 0/9] Add support for io_uring no-reply
2019-05-22 15:46 ` 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=20190521235215.31341-1-mehta.aaru20@gmail.com \
--to=mehta.aaru20@gmail.com \
--cc=jusual@mail.ru \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=saket.sinha89@gmail.com \
--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).