Skip to content

return nxt propagation within io-wq ctx

Pavel Begunkov io-uring lkml 2 versions In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest5 patches 2 repliesIn review
  2. v15 patches 0 repliesSuperseded

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/5io_uring: remove @nxt from the handlersfs/io_uring.c+86 -1590 replies
2/5io_uring/io-wq: pass *work instead of **workptrfs/io-wq.c fs/io-wq.h fs/io_uring.c+18 -200 replies
3/5io_uring/io-wq: allow put_work return next workfs/io-wq.c fs/io-wq.h fs/io_uring.c+32 -160 replies
4/5io_uring: remove extra nxt check after puntfs/io_uring.c+5 -50 replies
5/5io_uring: remove io_prep_next_work()fs/io_uring.c+1 -120 replies

Reviews trailers per patch

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

Read the v2 thread

Cover letter [PATCH REBASE v2 0/5] return nxt propagation within io-wq ctx

After io_put_req_find_next() was patched, handlers no more return next work, but enqueue them through io_queue_async_work() (mostly by io_put_work() -> io_put_req()). The patchset fixes that.

Patches 1-2 clean up and removes all futile attempts to get nxt from the opcode handlers. The 3rd one moves all this propagation idea into work->put_work(). And the rest ones are small clean up on top.

v2: rebase on top of poll changes

Pavel Begunkov (5):
io_uring: remove @nxt from the handlers
io_uring/io-wq: pass *work instead of **workptr
io_uring/io-wq: allow put_work return next work
io_uring: remove extra nxt check after punt
io_uring: remove io_prep_next_work()

 fs/io-wq.c    |  28 ++---
 fs/io-wq.h    |   4 +-
 fs/io_uring.c | 320 ++++++++++++++++++++------------------------------
 3 files changed, 141 insertions(+), 211 deletions(-)
Signature · 1 line
2.24.0