From: Thomas Gleixner <tglx@linutronix.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] task_work: cleanup notification modes
Date: Sat, 17 Oct 2020 17:31:42 +0200 [thread overview]
Message-ID: <87tuusj2ch.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <7e32aa44-35ff-3a48-87d0-8e7df586db1d@kernel.dk>
On Fri, Oct 16 2020 at 17:43, Jens Axboe wrote:
> On 10/16/20 5:38 PM, Thomas Gleixner wrote:
> If you know the task isn't exiting, then yeah you can ignore it. But
> seems a bit dicey...
Indeed.
>> fs/io_uring.c- if (unlikely(ret)) {
>> fs/io_uring.c- struct task_struct *tsk;
>> fs/io_uring.c-
>> fs/io_uring.c- init_task_work(&req->task_work, io_req_task_cancel);
>> fs/io_uring.c- tsk = io_wq_get_task(req->ctx->io_wq);
>> fs/io_uring.c: task_work_add(tsk, &req->task_work, 0);
>> fs/io_uring.c- wake_up_process(tsk);
>>
>> yet more magic wakeup.
>
> It's not magic, but probably needs a comment... If we fail, that task is
> exiting. But we know we have our io-wq threads, so we use that as a
> fallback. Not really expected in the fast path.
I somehow misread it. So ignore me.
Thanks,
tglx
next prev parent reply other threads:[~2020-10-17 15:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 15:16 [PATCH] task_work: cleanup notification modes Jens Axboe
2020-10-16 21:44 ` Thomas Gleixner
2020-10-16 22:39 ` Jens Axboe
2020-10-16 23:09 ` Thomas Gleixner
2020-10-16 23:13 ` Jens Axboe
2020-10-16 23:38 ` Thomas Gleixner
2020-10-16 23:43 ` Jens Axboe
2020-10-17 15:31 ` Thomas Gleixner [this message]
2020-10-17 15:36 ` Jens Axboe
2020-10-17 20:18 ` Thomas Gleixner
2020-10-17 20:32 ` Jens Axboe
2020-10-17 21:01 ` Thomas Gleixner
2020-10-17 21:03 ` Jens Axboe
2020-10-17 21:17 ` Thomas Gleixner
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=87tuusj2ch.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.