From: Jens Axboe <[email protected]>
To: Marcelo Diop-Gonzalez <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH liburing] Don't enter the kernel to wait on cqes if they are already available.
Date: Mon, 7 Dec 2020 08:41:37 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 12/3/20 9:07 AM, Marcelo Diop-Gonzalez wrote:
> In _io_uring_get_cqe(), if we can see from userspace that there are
> already wait_nr cqes available, then there is no need to call
> __sys_io_uring_enter2 (unless we have to submit IO or flush overflow),
> since the kernel will just end up returning immediately after
> performing the same check, anyway.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-12-07 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 16:07 [PATCH liburing] Don't enter the kernel to wait on cqes if they are already available Marcelo Diop-Gonzalez
2020-12-07 15:41 ` Jens Axboe [this message]
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 \
[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