aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin
diff options
context:
space:
mode:
authorPavel Begunkov <[email protected]>2024-03-18 22:00:29 +0000
committerJens Axboe <[email protected]>2024-04-15 08:10:24 -0600
commit92219afb980e01d88a1ac6d8fe01dcae255c4279 (patch)
tree95d35e41e2a0d2aaaa4f1611a65c9b9667617320 /tools/perf/scripts/python/bin
parent6e6b8c62120a22acd8cb759304e4cd2e3215d488 (diff)
io_uring: force tw ctx locking
We can run normal task_work without locking the ctx, however we try to lock anyway and most handlers prefer or require it locked. It might have been interesting to multi-submitter ring with high contention completing async read/write requests via task_work, however that will still need to go through io_req_complete_post() and potentially take the lock for rsrc node putting or some other case. In other words, it's hard to care about it, so alawys force the locking. The case described would also because of various io_uring caches. Signed-off-by: Pavel Begunkov <[email protected]> Tested-by: Ming Lei <[email protected]> Link: https://lore.kernel.org/r/6ae858f2ef562e6ed9f13c60978c0d48926954ba.1710799188.git.asml.silence@gmail.com Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions