Re: [PATCHSET 0/5] io_uring restrictions cleanups and improvements

[Jens Axboe <axboe@kernel.dk>]

On Mon, 12 Jan 2026 08:14:40 -0700, Jens Axboe wrote:
> 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.
> 
> [...]

Applied, thanks!

[1/5] io_uring/register: have io_parse_restrictions() return number of ops
      commit: 51fff55a66d89d76fcaeaa277d53bdf5b19efa0e
[2/5] io_uring/register: have io_parse_restrictions() set restrictions enabled
      commit: e6ed0f051d557be5a782a42f74dddbc8ed5309ec
[3/5] io_uring/register: set ctx->restricted when restrictions are parsed
      commit: 09bd84421defa0a9dcebdcdaf8b7deb1870855d0
[4/5] io_uring: move ctx->restricted check into io_check_restriction()
      commit: 991fb85a1d43f0d0237a405d5535024f78a873e5
[5/5] io_uring: track restrictions separately for IORING_OP and IORING_REGISTER
      commit: d6406c45f14842019cfaaba19fe2a76ef9fa831c

Best regards,
-- 
Jens Axboe