From: [email protected] (Eric W. Biederman)
To: Jens Axboe <[email protected]>
Cc: [email protected], [email protected],
[email protected]
Subject: Re: [PATCH 01/18] io_uring: remove the need for relying on an io-wq fallback worker
Date: Fri, 19 Feb 2021 14:25:29 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]> (Jens Axboe's message of "Fri, 19 Feb 2021 10:09:53 -0700")
Jens Axboe <[email protected]> writes:
> We hit this case when the task is exiting, and we need somewhere to
> do background cleanup of requests. Instead of relying on the io-wq
> task manager to do this work for us, just stuff it somewhere where
> we can safely run it ourselves directly.
Minor nits below.
Eric
>
> Signed-off-by: Jens Axboe <[email protected]>
> ---
> fs/io-wq.c | 12 ------------
> fs/io-wq.h | 2 --
> fs/io_uring.c | 38 +++++++++++++++++++++++++++++++++++---
> 3 files changed, 35 insertions(+), 17 deletions(-)
>
> diff --git a/fs/io-wq.c b/fs/io-wq.c
> index c36bbcd823ce..800b299f9772 100644
> --- a/fs/io-wq.c
> +++ b/fs/io-wq.c
> @@ -16,7 +16,6 @@
> #include <linux/kthread.h>
> #include <linux/rculist_nulls.h>
> #include <linux/fs_struct.h>
> -#include <linux/task_work.h>
> #include <linux/blk-cgroup.h>
> #include <linux/audit.h>
> #include <linux/cpu.h>
> @@ -775,9 +774,6 @@ static int io_wq_manager(void *data)
> complete(&wq->done);
>
> while (!kthread_should_stop()) {
> - if (current->task_works)
> - task_work_run();
> -
> for_each_node(node) {
> struct io_wqe *wqe = wq->wqes[node];
> bool fork_worker[2] = { false, false };
> @@ -800,9 +796,6 @@ static int io_wq_manager(void *data)
> schedule_timeout(HZ);
> }
>
> - if (current->task_works)
> - task_work_run();
> -
> out:
> if (refcount_dec_and_test(&wq->refs)) {
> complete(&wq->done);
> @@ -1160,11 +1153,6 @@ void io_wq_destroy(struct io_wq *wq)
> __io_wq_destroy(wq);
> }
>
> -struct task_struct *io_wq_get_task(struct io_wq *wq)
> -{
> - return wq->manager;
> -}
> -
> static bool io_wq_worker_affinity(struct io_worker *worker, void *data)
> {
> struct task_struct *task = worker->task;
> diff --git a/fs/io-wq.h b/fs/io-wq.h
> index 096f1021018e..a1610702f222 100644
> --- a/fs/io-wq.h
> +++ b/fs/io-wq.h
> @@ -124,8 +124,6 @@ typedef bool (work_cancel_fn)(struct io_wq_work *, void *);
> enum io_wq_cancel io_wq_cancel_cb(struct io_wq *wq, work_cancel_fn *cancel,
> void *data, bool cancel_all);
>
> -struct task_struct *io_wq_get_task(struct io_wq *wq);
> -
> #if defined(CONFIG_IO_WQ)
> extern void io_wq_worker_sleeping(struct task_struct *);
> extern void io_wq_worker_running(struct task_struct *);
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index d951acb95117..bbd1ec7aa9e9 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -455,6 +455,9 @@ struct io_ring_ctx {
>
> struct io_restriction restrictions;
>
> + /* exit task_work */
> + struct callback_head *exit_task_work;
> +
> /* Keep this last, we don't need it for the fast path */
> struct work_struct exit_work;
> };
> @@ -2313,11 +2316,14 @@ static int io_req_task_work_add(struct io_kiocb *req)
> static void io_req_task_work_add_fallback(struct io_kiocb *req,
> task_work_func_t cb)
> {
> - struct task_struct *tsk = io_wq_get_task(req->ctx->io_wq);
> + struct io_ring_ctx *ctx = req->ctx;
> + struct callback_head *head;
>
> init_task_work(&req->task_work, cb);
> - task_work_add(tsk, &req->task_work, TWA_NONE);
> - wake_up_process(tsk);
> + do {
> + head = ctx->exit_task_work;
^^^^^^^^^^^^^^^^^^^^
This feels like this should be READ_ONCE to prevent tearing reads.
You use READ_ONCE on this same variable below which really suggests
this should be a READ_ONCE.
> + req->task_work.next = head;
> + } while (cmpxchg(&ctx->exit_task_work, head, &req->task_work) != head);
> }
>
> static void __io_req_task_cancel(struct io_kiocb *req, int error)
> @@ -9258,6 +9264,30 @@ void __io_uring_task_cancel(void)
> io_uring_remove_task_files(tctx);
> }
>
> +static void io_run_ctx_fallback(struct io_ring_ctx *ctx)
> +{
> + struct callback_head *work, *head, *next;
> +
> + do {
> + do {
> + head = NULL;
> + work = READ_ONCE(ctx->exit_task_work);
> + if (!work)
> + break;
> + } while (cmpxchg(&ctx->exit_task_work, work, head) != work);
> +
> + if (!work)
> + break;
Why the double break on "!work"? It seems like either the first should
be goto out, or only the second should be here.
> +
> + do {
> + next = work->next;
> + work->func(work);
> + work = next;
> + cond_resched();
> + } while (work);
> + } while (1);
> +}
> +
> static int io_uring_flush(struct file *file, void *data)
> {
> struct io_uring_task *tctx = current->io_uring;
> @@ -9268,6 +9298,8 @@ static int io_uring_flush(struct file *file, void *data)
> io_req_caches_free(ctx, current);
> }
>
> + io_run_ctx_fallback(ctx);
> +
> if (!tctx)
> return 0;
next prev parent reply other threads:[~2021-02-19 20:27 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 17:09 [PATCHSET RFC 0/18] Remove kthread usage from io_uring Jens Axboe
2021-02-19 17:09 ` [PATCH 01/18] io_uring: remove the need for relying on an io-wq fallback worker Jens Axboe
2021-02-19 20:25 ` Eric W. Biederman [this message]
2021-02-19 20:37 ` Jens Axboe
2021-02-22 13:46 ` Pavel Begunkov
2021-02-19 17:09 ` [PATCH 02/18] io-wq: don't create any IO workers upfront Jens Axboe
2021-02-19 17:09 ` [PATCH 03/18] io_uring: disable io-wq attaching Jens Axboe
2021-02-19 17:09 ` [PATCH 04/18] io-wq: get rid of wq->use_refs Jens Axboe
2021-02-19 17:09 ` [PATCH 05/18] io_uring: tie async worker side to the task context Jens Axboe
2021-02-20 8:11 ` Hao Xu
2021-02-20 14:38 ` Jens Axboe
2021-02-21 9:16 ` Hao Xu
2021-02-19 17:09 ` [PATCH 06/18] io-wq: don't pass 'wqe' needlessly around Jens Axboe
2021-02-19 17:09 ` [PATCH 07/18] arch: setup PF_IO_WORKER threads like PF_KTHREAD Jens Axboe
2021-02-19 22:21 ` Eric W. Biederman
2021-02-19 23:26 ` Jens Axboe
2021-02-19 17:10 ` [PATCH 08/18] kernel: treat PF_IO_WORKER like PF_KTHREAD for ptrace/signals Jens Axboe
2021-02-19 17:10 ` [PATCH 09/18] io-wq: fork worker threads from original task Jens Axboe
2021-03-04 12:23 ` Stefan Metzmacher
2021-03-04 13:05 ` Jens Axboe
2021-03-04 13:19 ` Stefan Metzmacher
2021-03-04 16:13 ` Stefan Metzmacher
2021-03-04 16:42 ` Jens Axboe
2021-03-04 17:09 ` Stefan Metzmacher
2021-03-04 17:32 ` Jens Axboe
2021-03-04 18:19 ` Jens Axboe
2021-03-04 18:56 ` Linus Torvalds
2021-03-04 19:19 ` Jens Axboe
2021-03-04 19:46 ` Linus Torvalds
2021-03-04 19:54 ` Jens Axboe
2021-03-04 20:00 ` Jens Axboe
2021-03-04 20:23 ` Jens Axboe
2021-03-04 20:50 ` Linus Torvalds
2021-03-04 20:54 ` Jens Axboe
2021-03-05 19:16 ` Eric W. Biederman
2021-03-05 19:00 ` Eric W. Biederman
2021-02-19 17:10 ` [PATCH 10/18] io-wq: worker idling always returns false Jens Axboe
2021-02-19 17:10 ` [PATCH 11/18] io_uring: remove any grabbing of context Jens Axboe
2021-02-19 17:10 ` [PATCH 12/18] io_uring: remove io_identity Jens Axboe
2021-02-19 17:10 ` [PATCH 13/18] io-wq: only remove worker from free_list, if it was there Jens Axboe
2021-02-19 17:10 ` [PATCH 14/18] io-wq: make io_wq_fork_thread() available to other users Jens Axboe
2021-02-19 17:10 ` [PATCH 15/18] io_uring: move SQPOLL thread io-wq forked worker Jens Axboe
2021-02-19 17:10 ` [PATCH 16/18] Revert "proc: don't allow async path resolution of /proc/thread-self components" Jens Axboe
2021-02-19 17:10 ` [PATCH 17/18] Revert "proc: don't allow async path resolution of /proc/self components" Jens Axboe
2021-02-19 17:10 ` [PATCH 18/18] net: remove cmsg restriction from io_uring based send/recvmsg calls Jens Axboe
2021-02-19 23:44 ` [PATCHSET RFC 0/18] Remove kthread usage from io_uring Stefan Metzmacher
2021-02-19 23:51 ` Jens Axboe
2021-02-21 5:04 ` Linus Torvalds
2021-02-21 21:22 ` 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