diff options
author | Jens Axboe <axboe@kernel.dk> | 2022-12-17 23:42:24 +0300 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2022-12-18 06:35:54 +0300 |
commit | 35d90f95cfa773b7e3b1f57ba15ce06a470f354c (patch) | |
tree | ee753101bc7a1ef45e98c6bc4cf9ff1d3536f97c /tools/perf/scripts/python/mem-phys-addr.py | |
parent | 6434ec0186b80c734aa7a2acf95f75f5c6dd943b (diff) | |
download | linux-35d90f95cfa773b7e3b1f57ba15ce06a470f354c.tar.xz |
io_uring: include task_work run after scheduling in wait for events
It's quite possible that we got woken up because task_work was queued,
and we need to process this task_work to generate the events waited for.
If we return to the wait loop without running task_work, we'll end up
adding the task to the waitqueue again, only to call
io_cqring_wait_schedule() again which will run the task_work. This is
less efficient than it could be, as it requires adding to the cq_wait
queue again. It also triggers the wakeup path for completions as
cq_wait is now non-empty with the task itself, and it'll require another
lock grab and deletion to remove ourselves from the waitqueue.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions