From: Stefan Roesch <[email protected]>
To: [email protected]
Cc: [email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected], Stefan Roesch <[email protected]>
Subject: [PATCH v6 0/3] io_uring: add napi busy polling support
Date: Wed, 1 Feb 2023 14:22:51 -0800 [thread overview]
Message-ID: <[email protected]> (raw)
From: Stefan Roesch <[email protected]>
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. For faster
access it also adds a hash table.
When a new napi id is added, the hash table is used to locate if
the napi id has already been added. When processing the busy poll
loop the list is used to process the individual elements.
io-uring allows specifying two parameters:
- busy poll timeout and
- prefer busy poll to call of io_napi_busy_loop()
This sets the above parameters for the ring. The settings are passed
with a new structure io_uring_napi.
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.
More detailled results are part of the commit message of the first
patch.
Changes:
- V6:
- Add a hash table on top of the list for faster access during the
add operation. The linked list and the hash table use the same
data structure
- V5:
- Refreshed to 6.1-rc6
- Use copy_from_user instead of memdup/kfree
- Removed the moving of napi_busy_poll_to
- Return -EINVAL if any of the reserved or padded fields are not 0.
- V4:
- Pass structure for napi config, instead of individual parameters
- V3:
- Refreshed to 6.1-rc5
- Added a new io-uring api for the prefer napi busy poll api and wire
it to io_napi_busy_loop().
- Removed the unregister (implemented as register)
- Added more performance results to the first commit message.
- V2:
- Add missing defines if CONFIG_NET_RX_BUSY_POLL is not defined
- Changes signature of function io_napi_add_list to static inline
if CONFIG_NET_RX_BUSY_POLL is not defined
- define some functions as static
Stefan Roesch (3):
io_uring: add napi busy polling support
io_uring: add api to set / get napi configuration.
io_uring: add api to set napi prefer busy poll
include/linux/io_uring_types.h | 10 ++
include/uapi/linux/io_uring.h | 12 ++
io_uring/io_uring.c | 300 +++++++++++++++++++++++++++++++++
io_uring/napi.h | 23 +++
io_uring/poll.c | 2 +
io_uring/sqpoll.c | 17 ++
6 files changed, 364 insertions(+)
create mode 100644 io_uring/napi.h
base-commit: c0b67534c95c537f7a506a06b98e5e85d72e2b7d
--
2.30.2
next reply other threads:[~2023-02-01 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 22:22 Stefan Roesch [this message]
2023-02-01 22:22 ` [PATCH v6 1/3] io_uring: add napi busy polling support Stefan Roesch
2023-02-01 22:22 ` [PATCH v6 2/3] io_uring: add api to set / get napi configuration Stefan Roesch
2023-02-01 23:15 ` Ammar Faizi
2023-02-02 18:47 ` Stefan Roesch
2023-02-01 22:22 ` [PATCH v6 3/3] io_uring: add api to set napi prefer busy poll 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] \
[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