From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Subject: [PATCHSET 0/5] io_uring restrictions cleanups and improvements
Date: Mon, 12 Jan 2026 08:14:40 -0700 [thread overview]
Message-ID: <20260112151905.200261-1-axboe@kernel.dk> (raw)
Hi,
In doing the task based restriction sets, I found myself doing a few
cleanups and improvements along the way. These really had nothing to
do with the added feature, hence I'm splitting them out into a
separate patchset.
This series is really 4 patches doing cleanup and preparation for
making it easier to add the task based restrictions, and patch 5 is
an improvement for how restrictions are checked. I ran some overhead
numbers and it's honestly surprisingly low for microbenchmarks. For
example, running a pure NOP workload at 13-15M op/sec, checking
restrictions is only about 1.5% of the CPU time. Never the less, I
suspect the most common restrictions applied is to limit the register
operations that can be done. Hence it makes sense to track whether
we have IORING_OP* or IORING_REGISTER* restrictions separately, so
it can be avoided to check ones op based restrictions if only register
based ones have been set.
include/linux/io_uring_types.h | 8 ++++++--
io_uring/io_uring.c | 6 ++++--
io_uring/register.c | 35 ++++++++++++++++++++++------------
3 files changed, 33 insertions(+), 16 deletions(-)
--
Jens Axboe
next reply other threads:[~2026-01-12 15:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 15:14 Jens Axboe [this message]
2026-01-12 15:14 ` [PATCH 1/5] io_uring/register: have io_parse_restrictions() return number of ops Jens Axboe
2026-01-12 15:14 ` [PATCH 2/5] io_uring/register: have io_parse_restrictions() set restrictions enabled Jens Axboe
2026-01-12 15:14 ` [PATCH 3/5] io_uring/register: set ctx->restricted when restrictions are parsed Jens Axboe
2026-01-12 15:14 ` [PATCH 4/5] io_uring: move ctx->restricted check into io_check_restriction() Jens Axboe
2026-01-12 15:14 ` [PATCH 5/5] io_uring: track restrictions separately for IORING_OP and IORING_REGISTER Jens Axboe
2026-01-13 17:27 ` [PATCHSET 0/5] io_uring restrictions cleanups and improvements Gabriel Krisman Bertazi
2026-01-13 18:22 ` Jens Axboe
2026-01-13 18:23 ` Jens Axboe
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=20260112151905.200261-1-axboe@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
/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