From: Stefan Roesch <[email protected]>
To: [email protected]
Cc: [email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected]
Subject: [RFC PATCH v2 1/4] liburing: add api to set napi busy poll timeout
Date: Mon, 7 Nov 2022 09:53:54 -0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
This adds the two functions to register and unregister the napi busy
poll timeout:
- io_uring_register_napi_busy_poll_timeout
- io_uring_unregister_napi_busy_poll_timeout
Signed-off-by: Stefan Roesch <[email protected]>
---
src/include/liburing.h | 4 ++++
src/include/liburing/io_uring.h | 4 ++++
src/liburing.map | 8 ++++++++
src/register.c | 15 +++++++++++++++
4 files changed, 31 insertions(+)
diff --git a/src/include/liburing.h b/src/include/liburing.h
index 12a703f..6722fa2 100644
--- a/src/include/liburing.h
+++ b/src/include/liburing.h
@@ -235,6 +235,10 @@ int io_uring_register_sync_cancel(struct io_uring *ring,
int io_uring_register_file_alloc_range(struct io_uring *ring,
unsigned off, unsigned len);
+int io_uring_register_napi_busy_poll_timeout(struct io_uring *ring,
+ unsigned int to);
+int io_uring_unregister_napi_busy_poll_timeout(struct io_uring *ring);
+
int io_uring_get_events(struct io_uring *ring);
int io_uring_submit_and_get_events(struct io_uring *ring);
diff --git a/src/include/liburing/io_uring.h b/src/include/liburing/io_uring.h
index a3e0920..0919d9e 100644
--- a/src/include/liburing/io_uring.h
+++ b/src/include/liburing/io_uring.h
@@ -499,6 +499,10 @@ enum {
/* register a range of fixed file slots for automatic slot allocation */
IORING_REGISTER_FILE_ALLOC_RANGE = 25,
+ /* set/clear busy poll timeout */
+ IORING_REGISTER_NAPI_BUSY_POLL_TIMEOUT = 26,
+ IORING_UNREGISTER_NAPI_BUSY_POLL_TIMEOUT= 27,
+
/* this goes last */
IORING_REGISTER_LAST
};
diff --git a/src/liburing.map b/src/liburing.map
index 06c64f8..793766e 100644
--- a/src/liburing.map
+++ b/src/liburing.map
@@ -60,6 +60,8 @@ LIBURING_2.3 {
global:
io_uring_register_sync_cancel;
io_uring_register_file_alloc_range;
+ io_uring_register_busy_poll_timeout;
+ io_uring_unregister_busy_poll_timeout;
io_uring_enter;
io_uring_enter2;
io_uring_setup;
@@ -67,3 +69,9 @@ LIBURING_2.3 {
io_uring_get_events;
io_uring_submit_and_get_events;
} LIBURING_2.2;
+
+LIBURING_2.4 {
+ global:
+ io_uring_napi_register_busy_poll_timeout;
+ io_uring_napi_unregister_busy_poll_timeout;
+} LIBURING_2.3;
diff --git a/src/register.c b/src/register.c
index e849825..ffbfb8a 100644
--- a/src/register.c
+++ b/src/register.c
@@ -367,3 +367,18 @@ int io_uring_register_file_alloc_range(struct io_uring *ring,
IORING_REGISTER_FILE_ALLOC_RANGE, &range,
0);
}
+
+int io_uring_register_napi_busy_poll_timeout(struct io_uring *ring,
+ unsigned int to)
+{
+ return __sys_io_uring_register(ring->ring_fd,
+ IORING_REGISTER_NAPI_BUSY_POLL_TIMEOUT,
+ NULL, to);
+}
+
+int io_uring_unregister_napi_busy_poll_timeout(struct io_uring *ring)
+{
+ return __sys_io_uring_register(ring->ring_fd,
+ IORING_UNREGISTER_NAPI_BUSY_POLL_TIMEOUT,
+ NULL, 0);
+}
--
2.30.2
next prev parent reply other threads:[~2022-11-07 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 17:53 [RFC PATCH v2 0/4] liburing: add api for napi busy poll timeout Stefan Roesch
2022-11-07 17:53 ` Stefan Roesch [this message]
2022-11-08 7:14 ` [RFC PATCH v2 1/4] liburing: add api to set " Ammar Faizi
2022-11-07 17:53 ` [RFC PATCH v2 2/4] liburing: add documentation for new napi busy polling Stefan Roesch
2022-11-08 8:04 ` Ammar Faizi
2022-11-07 17:53 ` [RFC PATCH v2 3/4] liburing: add test programs for napi busy poll Stefan Roesch
2022-11-08 7:01 ` Ammar Faizi
2022-11-08 9:47 ` Ammar Faizi
2022-11-07 17:53 ` [RFC PATCH v2 4/4] liburing: update changelog with new feature 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