qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Sam Li <faithilikerun@gmail.com>
To: Stefan Hajnoczi <stefanha@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 19:34:03 +0800	[thread overview]
Message-ID: <CAAAx-8KBk2tzaJRfYtAbsAGSAvY4z+SsV2BxtRBO7mqVvmLW_w@mail.gmail.com> (raw)
In-Reply-To: <YpX8q9XrnTehFu7N@stefanha-x1.localdomain>

Stefan Hajnoczi <stefanha@gmail.com> 于2022年5月31日周二 19:31写道:
>
> 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
>

Great! Sorry about the mistake before. I'm flushed.


> Stefan


  reply	other threads:[~2022-05-31 11:43 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
2022-05-31 11:34   ` Sam Li [this message]
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=CAAAx-8KBk2tzaJRfYtAbsAGSAvY4z+SsV2BxtRBO7mqVvmLW_w@mail.gmail.com \
    --to=faithilikerun@gmail.com \
    --cc=Dmitry.Fomichev@wdc.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=hare@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).