From: Stefan Hajnoczi <stefanha@gmail.com>
To: Sam Li <faithilikerun@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Dmitry Fomichev <Dmitry.Fomichev@wdc.com>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH v6] Use io_uring_register_ring_fd() to skip fd operations
Date: Tue, 31 May 2022 12:31:55 +0100 [thread overview]
Message-ID: <YpX8q9XrnTehFu7N@stefanha-x1.localdomain> (raw)
In-Reply-To: <20220531105011.111082-1-faithilikerun@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
On Tue, May 31, 2022 at 06:50:11PM +0800, Sam Li wrote:
> Linux recently added a new io_uring(7) optimization API that QEMU
> doesn't take advantage of yet. The liburing library that QEMU uses
> has added a corresponding new API calling io_uring_register_ring_fd().
> When this API is called after creating the ring, the io_uring_submit()
> library function passes a flag to the io_uring_enter(2) syscall
> allowing it to skip the ring file descriptor fdget()/fdput()
> operations. This saves some CPU cycles.
>
> Signed-off-by: Sam Li <faithilikerun@gmail.com>
> ---
> block/io_uring.c | 12 +++++++++++-
> meson.build | 1 +
> 2 files changed, 12 insertions(+), 1 deletion(-)
Thanks, applied to my block tree:
https://gitlab.com/stefanha/qemu/commits/block
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-05-31 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 10:50 [PATCH v6] Use io_uring_register_ring_fd() to skip fd operations Sam Li
2022-05-31 11:31 ` Stefan Hajnoczi [this message]
2022-05-31 11:34 ` Sam Li
2022-05-31 11:50 ` 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=YpX8q9XrnTehFu7N@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=Dmitry.Fomichev@wdc.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=faithilikerun@gmail.com \
--cc=hare@suse.de \
--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).