From: Ming Lei <[email protected]>
To: Stefan Hajnoczi <[email protected]>
Cc: "Richard W.M. Jones" <[email protected]>,
Stefan Hajnoczi <[email protected]>,
[email protected], [email protected],
[email protected],
Kirill Tkhai <[email protected]>,
Manuel Bentele <[email protected]>,
[email protected], Kevin Wolf <[email protected]>,
Xie Yongji <[email protected]>,
"Denis V. Lunev" <[email protected]>,
Stefano Garzarella <[email protected]>
Subject: Re: ublk-qcow2: ublk-qcow2 is available
Date: Thu, 13 Oct 2022 09:50:55 +0800 [thread overview]
Message-ID: <Y0du/9K3II70tZTD@T590> (raw)
In-Reply-To: <CAJSP0QXbnhkVgfgMfC=MAyvF63Oof_ZGDvNFhniDCvVY-f6Hmw@mail.gmail.com>
On Wed, Oct 12, 2022 at 10:15:28AM -0400, Stefan Hajnoczi wrote:
> On Thu, 6 Oct 2022 at 06:14, Richard W.M. Jones <[email protected]> wrote:
> >
> > On Tue, Oct 04, 2022 at 09:53:32AM -0400, Stefan Hajnoczi wrote:
> > > qemu-nbd doesn't use io_uring to handle the backend IO,
> >
> > Would this be fixed by your (not yet upstream) libblkio driver for
> > qemu?
>
> I was wrong, qemu-nbd has syntax to use io_uring:
>
> $ qemu-nbd ... --image-opts driver=file,filename=test.img,aio=io_uring
Yeah, I saw the option, previously when I tried io_uring via:
qemu-nbd -c /dev/nbd11 -n --aio=io_uring $my_file
It complains that 'qemu-nbd: Invalid aio mode 'io_uring'' even though
that 'qemu-nbd --help' does say that io_uring is supported.
Today just tried it on Fedora 37, looks it starts working with
--aio=io_uring, but the IOPS is basically same with --aio=native, and
IO trace shows that io_uring is used by qemu-nbd.
Thanks,
Ming
next prev parent reply other threads:[~2022-10-13 1:51 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 9:24 ublk-qcow2: ublk-qcow2 is available Ming Lei
2022-10-03 19:53 ` Stefan Hajnoczi
2022-10-03 23:57 ` Denis V. Lunev
2022-10-05 15:11 ` Stefan Hajnoczi
2022-10-06 10:26 ` Ming Lei
2022-10-06 13:59 ` Stefan Hajnoczi
2022-10-06 15:09 ` Ming Lei
2022-10-06 18:29 ` Stefan Hajnoczi
2022-10-07 11:21 ` Ming Lei
2022-10-04 9:43 ` Ming Lei
2022-10-04 13:53 ` Stefan Hajnoczi
2022-10-05 4:18 ` Ming Lei
2022-10-05 12:21 ` Stefan Hajnoczi
2022-10-05 12:38 ` Denis V. Lunev
2022-10-06 11:24 ` Ming Lei
2022-10-07 10:04 ` Yongji Xie
2022-10-07 10:51 ` Ming Lei
2022-10-07 11:21 ` Yongji Xie
2022-10-07 11:23 ` Ming Lei
2022-10-08 8:43 ` Ziyang Zhang
2022-10-12 14:22 ` Stefan Hajnoczi
2022-10-13 6:48 ` Yongji Xie
2022-10-13 16:02 ` Stefan Hajnoczi
2022-10-14 12:56 ` Ming Lei
2022-10-17 11:11 ` Yongji Xie
2022-10-18 6:59 ` Ming Lei
2022-10-18 13:17 ` Yongji Xie
2022-10-18 14:54 ` Stefan Hajnoczi
2022-10-19 9:09 ` Ming Lei
2022-10-24 16:11 ` Stefan Hajnoczi
2022-10-21 5:33 ` Yongji Xie
2022-10-21 6:30 ` Jason Wang
2022-10-25 8:17 ` Yongji Xie
2022-10-25 12:02 ` Stefan Hajnoczi
2022-10-28 13:33 ` Yongji Xie
2022-11-01 2:36 ` Jason Wang
2022-11-02 19:13 ` Stefan Hajnoczi
2022-11-04 6:55 ` Jason Wang
2022-10-21 6:28 ` Jason Wang
2022-10-06 10:14 ` Richard W.M. Jones
2022-10-12 14:15 ` Stefan Hajnoczi
2022-10-13 1:50 ` Ming Lei [this message]
2022-10-13 16:01 ` Stefan Hajnoczi
2022-10-04 5:43 ` Manuel Bentele
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=Y0du/9K3II70tZTD@T590 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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