Skip to content

optimise submit+iopoll mutex locking

Pavel Begunkov io-uring 1 version Applied

Status from this message: Applied, thanks!

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 1 replyApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/3io_uring: split off IOPOLL argument verifictionfs/io_uring.c+22 -70 replies
2/3io_uring: pre-calculate syscall iopolling decisionfs/io_uring.c+13 -80 replies
3/3io_uring: optimise mutex locking for submit+iopollfs/io_uring.c+23 -170 replies

Reviews trailers per patch

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

Read the v1 thread

Cover letter [PATCH 0/3] optimise submit+iopoll mutex locking

This saves one mutex lock/unlock pair per syscall when users do submit + getevents. Perf tells that for QD1 iopoll this patch reduces overhead on locking from ~4.3% to ~2.6%, iow cuts 1.3% - 1.9% of CPU time. Something similar I see in final throughput.

It's a good win for smaller QD, especially considering that io_uring only takes about 20-30% of all cycles, the rest goes to syscalling, the block layer and below.

Pavel Begunkov (3):
io_uring: split off IOPOLL argument verifiction
io_uring: pre-calculate syscall iopolling decision
io_uring: optimise mutex locking for submit+iopoll

 fs/io_uring.c | 86 +++++++++++++++++++++++++++++++++------------------
 1 file changed, 56 insertions(+), 30 deletions(-)
Signature · 1 line
2.35.1