From: Hao Xu <[email protected]>
To: Jens Axboe <[email protected]>
Cc: [email protected], Pavel Begunkov <[email protected]>,
Joseph Qi <[email protected]>
Subject: [PATCH for-5.13] io_uring: maintain drain requests' logic
Date: Wed, 31 Mar 2021 17:01:02 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
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 a simple solution is to ignore all multishot poll cqes, which means
drain requests won't wait those request to be done.
Signed-off-by: Hao Xu <[email protected]>
---
fs/io_uring.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/fs/io_uring.c b/fs/io_uring.c
index 513096759445..cd6d44cf5940 100644
--- a/fs/io_uring.c
+++ b/fs/io_uring.c
@@ -455,6 +455,7 @@ struct io_ring_ctx {
struct callback_head *exit_task_work;
struct wait_queue_head hash_wait;
+ unsigned multishot_cqes;
/* Keep this last, we don't need it for the fast path */
struct work_struct exit_work;
@@ -1181,8 +1182,8 @@ static bool req_need_defer(struct io_kiocb *req, u32 seq)
if (unlikely(req->flags & REQ_F_IO_DRAIN)) {
struct io_ring_ctx *ctx = req->ctx;
- return seq != ctx->cached_cq_tail
- + READ_ONCE(ctx->cached_cq_overflow);
+ return seq + ctx->multishot_cqes != ctx->cached_cq_tail
+ + READ_ONCE(ctx->cached_cq_overflow);
}
return false;
@@ -4897,6 +4898,7 @@ static bool io_poll_complete(struct io_kiocb *req, __poll_t mask, int error)
{
struct io_ring_ctx *ctx = req->ctx;
unsigned flags = IORING_CQE_F_MORE;
+ bool multishot_poll = !(req->poll.events & EPOLLONESHOT);
if (!error && req->poll.canceled) {
error = -ECANCELED;
@@ -4911,6 +4913,9 @@ static bool io_poll_complete(struct io_kiocb *req, __poll_t mask, int error)
req->poll.done = true;
flags = 0;
}
+ if (multishot_poll)
+ ctx->multishot_cqes++;
+
io_commit_cqring(ctx);
return !(flags & IORING_CQE_F_MORE);
}
--
1.8.3.1
next reply other threads:[~2021-03-31 9:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 9:01 Hao Xu [this message]
2021-03-31 15:36 ` [PATCH for-5.13] io_uring: maintain drain requests' logic Jens Axboe
2021-04-01 6:58 ` Hao Xu
2021-03-31 22:06 ` Pavel Begunkov
2021-04-01 6:53 ` Hao Xu
2021-04-01 10:25 ` Pavel Begunkov
[not found] ` <[email protected]>
2021-04-01 22:29 ` Pavel Begunkov
2021-04-03 6:58 ` Hao Xu
2021-04-04 23:07 ` Jens Axboe
2021-04-05 16:11 ` Hao Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1617181262-66724-1-git-send-email-haoxu@linux.alibaba.com \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox