From: Jens Axboe <[email protected]>
To: [email protected]
Cc: [email protected], [email protected]
Subject: [PATCHSET 0/2] tw/wakeup tweaks
Date: Sat, 17 Dec 2022 13:48:38 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
One patch tweaks when we think we have task_work pending to be more
inclusive rather than gate on TIF_NOTIFY_SIGNAL, patch two ensures we
don't do extra loops io_cqring_wait() - and just as importantly, that
the expected run path for task_work will not have the task itself
adding to the ctx->cq_wait waitqueue.
--
Jens Axboe
next reply other threads:[~2022-12-17 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 20:48 Jens Axboe [this message]
2022-12-17 20:48 ` [PATCH 1/2] io_uring: don't use TIF_NOTIFY_SIGNAL to test for availability of task_work Jens Axboe
2022-12-17 20:48 ` [PATCH 2/2] io_uring: include task_work run after scheduling in wait for events Jens Axboe
2022-12-18 3:37 ` [PATCH v2 " 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] \
/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