Skip to content

Cache tctx cancelation state in the ctx

Jens Axboe io-uring 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest4 patches 1 replyIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4io_uring: consolidate the put_ref-and-return section of adding workio_uring/io_uring.c+6 -60 replies
2/4io_uring: rename 'in_idle' to 'in_cancel'include/linux/io_uring_types.h io_uring/io_uring.c io_uring/tctx.c+11 -110 replies
3/4io_uring: cache task cancelation state in the ctxinclude/linux/io_uring_types.h io_uring/io_uring.c+44 -21 reply
4/4io_uring: use local ctx cancelation state for io_req_local_work_add()io_uring/io_uring.c+1 -10 replies

Reviews trailers per patch

1 of 4 patches has a Reviewed-by or Acked-by.

PatchGabriel Krisman Bertazi
1/4
2/4
3/4R-b
4/4

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/4] Cache tctx cancelation state in the ctx

Hi,

One of the more expensive parts of io_req_local_work_add() is that it has to pull in the remote task tctx to check for the very unlikely event that we are in a cancelation state.

Cache the cancelation state in each ctx instead. This makes the marking of cancelation (and clearing) a bit more expensive, but those are very slow path operations. The upside is that io_req_local_work_add() becomes a lot cheaper, which is what we care about.

Signature · 1 line
Jens Axboe