Skip to content

add persistent submission state

Pavel Begunkov io-uring lkml 3 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v3 Latest6 patches 5 repliesIn review
  2. v28 patches 0 repliesSuperseded
  3. v18 patches 0 repliesSuperseded

Patches in v3 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/6io_uring: always pass non-null io_submit_statefs/io_uring.c+12 -210 replies
2/6io_uring: place io_submit_state into ctxfs/io_uring.c+40 -350 replies
3/6io_uring: move ring_fd into io_submit_statefs/io_uring.c+13 -100 replies
4/6io_uring: move *link into io_submit_statefs/io_uring.c+12 -100 replies
5/6io_uring: persistent req bulk allocation cachefs/io_uring.c+22 -60 replies
6/6io_uring: optimise req bulk allocation cachefs/io_uring.c+3 -80 replies

Reviews trailers per patch

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

Read the v3 thread

Cover letter [PATCH v3 0/6] add persistent submission state

Apart from unrelated first patch, this persues two goals:

1. start preparing io_uring to move resources handling into opcode specific functions

2. make the first step towards long-standing optimisation ideas

Basically, it makes struct io_submit_state embedded into ctx, so easily accessible and persistent, and then plays a bit around that.

v2: rebase
v3: drop the mm-related patch and rebase

Pavel Begunkov (6):
io_uring: always pass non-null io_submit_state
io_uring: place io_submit_state into ctx
io_uring: move ring_fd into io_submit_state
io_uring: move *link into io_submit_state
io_uring: persistent req bulk allocation cache
io_uring: optimise req bulk allocation cache

 fs/io_uring.c | 166 +++++++++++++++++++++++++++-----------------------
 1 file changed, 89 insertions(+), 77 deletions(-)
Signature · 1 line
2.24.0