All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aarushi Mehta <mehta.aaru20@gmail.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, saket.sinha89@gmail.com,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Julia Suvorova <jusual@mail.ru>,
	Aarushi Mehta <mehta.aaru20@gmail.com>
Subject: [Qemu-devel] [RFC PATCH v2 7/9] blockdev: accept io_uring as option
Date: Fri, 24 May 2019 19:33:35 +0530	[thread overview]
Message-ID: <20190524140337.13415-8-mehta.aaru20@gmail.com> (raw)
In-Reply-To: <20190524140337.13415-1-mehta.aaru20@gmail.com>

Signed-off-by: Aarushi Mehta <mehta.aaru20@gmail.com>
---
 blockdev.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/blockdev.c b/blockdev.c
index 79fbac8450..b44b9d660d 100644
--- a/blockdev.c
+++ b/blockdev.c
@@ -386,6 +386,8 @@ static void extract_common_blockdev_options(QemuOpts *opts, int *bdrv_flags,
         if ((aio = qemu_opt_get(opts, "aio")) != NULL) {
             if (!strcmp(aio, "native")) {
                 *bdrv_flags |= BDRV_O_NATIVE_AIO;
+            } else if (!strcmp(aio, "io_uring")) {
+                *bdrv_flags |= BDRV_O_IO_URING;
             } else if (!strcmp(aio, "threads")) {
                 /* this is the default */
             } else {
@@ -4547,7 +4549,7 @@ QemuOptsList qemu_common_drive_opts = {
         },{
             .name = "aio",
             .type = QEMU_OPT_STRING,
-            .help = "host AIO implementation (threads, native)",
+            .help = "host AIO implementation (threads, native, io_uring)",
         },{
             .name = BDRV_OPT_CACHE_WB,
             .type = QEMU_OPT_BOOL,
--
2.17.1


  parent reply	other threads:[~2019-05-24 14:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-24 14:03 [Qemu-devel] [RFC PATCH v2 0/9] Add support for io_uring Aarushi Mehta
2019-05-24 14:03 ` [Qemu-devel] [RFC PATCH v2 1/9] qapi/block-core: add option " Aarushi Mehta
2019-05-24 15:12   ` Stefan Hajnoczi
2019-05-24 16:17     ` Markus Armbruster
2019-05-24 14:03 ` [Qemu-devel] [RFC PATCH v2 2/9] block/block: add BDRV flag " Aarushi Mehta
2019-05-24 15:12   ` Stefan Hajnoczi
2019-05-24 14:03 ` [Qemu-devel] [RFC PATCH v2 3/9] include/block: declare interfaces " Aarushi Mehta
2019-05-24 15:16   ` Stefan Hajnoczi
2019-05-24 14:03 ` [Qemu-devel] [RFC PATCH v2 4/9] stubs: add aio interface stubs " Aarushi Mehta
2019-05-24 15:24   ` Stefan Hajnoczi
2019-05-24 14:03 ` [Qemu-devel] [RFC PATCH v2 5/9] util/async: add aio interfaces " Aarushi Mehta
2019-05-24 15:25   ` Stefan Hajnoczi
2019-05-24 14:03 ` [Qemu-devel] [RFC PATCH v2 6/9] block/io_uring: implements " Aarushi Mehta
2019-05-24 16:17   ` Stefan Hajnoczi
2019-05-24 14:03 ` Aarushi Mehta [this message]
2019-05-24 16:17   ` [Qemu-devel] [RFC PATCH v2 7/9] blockdev: accept io_uring as option Stefan Hajnoczi
2019-05-24 14:03 ` [Qemu-devel] [RFC PATCH v2 8/9] block/file-posix: extends to use with io_uring Aarushi Mehta
2019-05-24 16:19   ` Stefan Hajnoczi
2019-05-24 14:03 ` [Qemu-devel] [RFC PATCH v2 9/9] configure: permit use of io_uring Aarushi Mehta
2019-05-24 16:20   ` 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=20190524140337.13415-8-mehta.aaru20@gmail.com \
    --to=mehta.aaru20@gmail.com \
    --cc=jusual@mail.ru \
    --cc=kwolf@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.