From: Pavel Begunkov <[email protected]>
To: Hao Xu <[email protected]>, Jens Axboe <[email protected]>
Cc: [email protected], Joseph Qi <[email protected]>
Subject: Re: [PATCH 5/5] io_uring: batch completion in prior_task_list
Date: Tue, 7 Dec 2021 21:01:25 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 12/7/21 09:39, Hao Xu wrote:
> In previous patches, we have already gathered some tw with
> io_req_task_complete() as callback in prior_task_list, let's complete
> them in batch while we cannot grab uring lock. In this way, we batch
> the req_complete_post path.
>
> Tested-by: Pavel Begunkov <[email protected]>
Hao, please never add tags for other people unless they confirmed
that it's fine. I asked Jens to kill this one and my signed-off
from 4/5 from io_uring branches.
> Signed-off-by: Hao Xu <[email protected]>
> ---
>
> Hi Pavel,
> May I add the above Test-by tag here?
>
> fs/io_uring.c | 70 +++++++++++++++++++++++++++++++++++++++++++--------
> 1 file changed, 60 insertions(+), 10 deletions(-)
>
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 21738ed7521e..f224f8df77a1 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -2225,6 +2225,49 @@ static void ctx_flush_and_put(struct io_ring_ctx *ctx, bool *locked)
> percpu_ref_put(&ctx->refs);
> }
>
> +static inline void ctx_commit_and_unlock(struct io_ring_ctx *ctx)
> +{
> + io_commit_cqring(ctx);
> + spin_unlock(&ctx->completion_lock);
> + io_cqring_ev_posted(ctx);
> +}
> +
> +static void handle_prior_tw_list(struct io_wq_work_node *node, struct io_ring_ctx **ctx,
> + bool *uring_locked, bool *compl_locked)
compl_locked probably can be a local var here, you're clearing it at the
end of the function anyway.
> +{
> + do {
> + struct io_wq_work_node *next = node->next;
> + struct io_kiocb *req = container_of(node, struct io_kiocb,
> + io_task_work.node);
> +
> + if (req->ctx != *ctx) {
> + if (unlikely(*compl_locked)) {
> + ctx_commit_and_unlock(*ctx);
> + *compl_locked = false;
> + }
> + ctx_flush_and_put(*ctx, uring_locked);
> + *ctx = req->ctx;
> + /* if not contended, grab and improve batching */
> + *uring_locked = mutex_trylock(&(*ctx)->uring_lock);
> + percpu_ref_get(&(*ctx)->refs);
> + if (unlikely(!*uring_locked)) {
> + spin_lock(&(*ctx)->completion_lock);
> + *compl_locked = true;
> + }
> + }
> + if (likely(*uring_locked))
> + req->io_task_work.func(req, uring_locked);
> + else
> + __io_req_complete_post(req, req->result, io_put_kbuf(req));
I think there is the same issue as last time, first iteration of tctx_task_work()
sets ctx but doesn't get uring_lock. Then you go here, find a request with the
same ctx and end up here with locking.
> + node = next;
> + } while (node);
> +
> + if (unlikely(*compl_locked)) {
> + ctx_commit_and_unlock(*ctx);
> + *compl_locked = false;
> + }
> +}
--
Pavel Begunkov
next prev parent reply other threads:[~2021-12-07 21:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 9:39 [PATCH v7 0/5] task optimization Hao Xu
2021-12-07 9:39 ` [PATCH 1/5] io-wq: add helper to merge two wq_lists Hao Xu
2021-12-07 9:39 ` [PATCH 2/5] io_uring: add a priority tw list for irq completion work Hao Xu
2021-12-07 9:39 ` [PATCH 3/5] io_uring: add helper for task work execution code Hao Xu
2021-12-07 9:39 ` [PATCH 4/5] io_uring: split io_req_complete_post() and add a helper Hao Xu
2021-12-07 9:39 ` [PATCH 5/5] io_uring: batch completion in prior_task_list Hao Xu
2021-12-07 21:01 ` Pavel Begunkov [this message]
2021-12-07 21:16 ` Pavel Begunkov
2021-12-08 5:04 ` Hao Xu
2021-12-08 5:08 ` Hao Xu
2021-12-07 21:59 ` Jens Axboe
2021-12-08 5:23 ` Hao Xu
2021-12-07 11:18 ` [PATCH v7 0/5] task optimization Hao Xu
2021-12-07 16:48 ` Jens Axboe
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 \
[email protected] \
[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