aboutsummaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorHao Xu <haoxu@linux.alibaba.com>2021-04-13 15:20:39 +0800
committerJens Axboe <axboe@kernel.dk>2021-04-27 07:38:58 -0600
commit7b289c38335ec7bebe45ed31137d596c808e23ac (patch)
tree5e9b1321046c439869ba6a328d46806150876945 /kernel
parentio_uring: Check current->io_uring in io_uring_cancel_sqpoll (diff)
downloadlinux-dev-7b289c38335ec7bebe45ed31137d596c808e23ac.tar.xz
linux-dev-7b289c38335ec7bebe45ed31137d596c808e23ac.zip
io_uring: maintain drain logic for multishot poll requests
Now that we have multishot poll requests, one SQE can emit multiple CQEs. given below example: sqe0(multishot poll)-->sqe1-->sqe2(drain req) sqe2 is designed to issue after sqe0 and sqe1 completed, but since sqe0 is a multishot poll request, sqe2 may be issued after sqe0's event triggered twice before sqe1 completed. This isn't what users leverage drain requests for. Here the solution is to wait for multishot poll requests fully completed. To achieve this, we should reconsider the req_need_defer equation, the original one is: all_sqes(excluding dropped ones) == all_cqes(including dropped ones) This means we issue a drain request when all the previous submitted SQEs have generated their CQEs. Now we should consider multishot requests, we deduct all the multishot CQEs except the cancellation one, In this way a multishot poll request behave like a normal request, so: all_sqes == all_cqes - multishot_cqes(except cancellations) Here we introduce cq_extra for it. Signed-off-by: Hao Xu <haoxu@linux.alibaba.com> Link: https://lore.kernel.org/r/1618298439-136286-1-git-send-email-haoxu@linux.alibaba.com Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions