Skip to content

Remove IRQ safety of completion_lock

Jens Axboe io-uring 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest4 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4io_uring: run timeouts from task_workfs/io_uring.c+31 -120 replies
2/4io_uring: run linked timeouts from task_workfs/io_uring.c+30 -120 replies
3/4io_uring: run regular file completions from task_workfs/io_uring.c+24 -70 replies
4/4io_uring: remove IRQ aspect of io_ring_ctx completion lockfs/io_uring.c+72 -770 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCHSET 0/4] Remove IRQ safety of completion_lock

Hi,

Out of all the request types we support, we only really have a few that complete from interrupt context. Yet due to those, we end up needing to make the completion_lock IRQ safe. If we move those completions through our task_work infastructure, then we can get rid of the need to have the completion_lock be IRQ safe. That has benefits for all users.

Signature · 1 line
Jens Axboe