From: Stefan Roesch <[email protected]>
To: [email protected]
Cc: [email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected]
Subject: [RFC PATCH v1 0/2] io_uring: add napi busy polling support
Date: Thu, 3 Nov 2022 13:39:37 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
This adds the napi busy polling support in io_uring.c. It adds a new
napi_list to the io_ring_ctx structure. This list contains the list of
napi_id's that are currently enabled for busy polling. This list is
used to determine which napi id's enabled busy polling.
To set the new napi busy poll timeout, a new io-uring api has been
added. It sets the napi busy poll timeout for the corresponding ring.
There is also a corresponding liburing patch series, which enables this
feature. The name of the series is "liburing: add add api for napi busy
poll timeout". It also contains two programs to test the this.
Testing has shown that the round-trip times are reduced to 38us from
55us by enabling napi busy polling with a busy poll timeout of 100us.
Signed-off-by: Stefan Roesch <[email protected]>
Stefan Roesch (2):
io_uring: add napi busy polling support
io_uring: add api to set napi busy poll timeout.
include/linux/io_uring_types.h | 6 +
include/uapi/linux/io_uring.h | 4 +
io_uring/io_uring.c | 255 +++++++++++++++++++++++++++++++++
io_uring/napi.h | 22 +++
io_uring/poll.c | 3 +
io_uring/sqpoll.c | 9 ++
6 files changed, 299 insertions(+)
create mode 100644 io_uring/napi.h
base-commit: 8f71a2b3f435f29b787537d1abedaa7d8ebe6647
--
2.30.2
next reply other threads:[~2022-11-03 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 20:39 Stefan Roesch [this message]
2022-11-03 20:39 ` [RFC PATCH v1 1/2] io_uring: add napi busy polling support Stefan Roesch
2022-11-03 20:39 ` [RFC PATCH v1 2/2] io_uring: add api to set napi busy poll timeout Stefan Roesch
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] \
[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