summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorMing Lei <ming.lei@redhat.com>2025-04-16 06:54:37 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-05-02 09:02:13 +0300
commit3bae87bf5af394359313c4580b4acbc3068b3f39 (patch)
tree96d582efa29ecdedb944bd9a02be1224c8d33707 /tools/perf/scripts/python/export-to-postgresql.py
parentdb1380ad45f76df644761336414c3efc48156251 (diff)
downloadlinux-3bae87bf5af394359313c4580b4acbc3068b3f39.tar.xz
ublk: rely on ->canceling for dealing with ublk_nosrv_dev_should_queue_io
[ Upstream commit 7e26cb69c5e62152a6f05a2ae23605a983a8ef31 ] Now ublk deals with ublk_nosrv_dev_should_queue_io() by keeping request queue as quiesced. This way is fragile because queue quiesce crosses syscalls or process contexts. Switch to rely on ubq->canceling for dealing with ublk_nosrv_dev_should_queue_io(), because it has been used for this purpose during io_uring context exiting, and it can be reused before recovering too. In ublk_queue_rq(), the request will be added to requeue list without kicking off requeue in case of ubq->canceling, and finally requests added in requeue list will be dispatched from either ublk_stop_dev() or ublk_ctrl_end_recovery(). Meantime we have to move reset of ubq->canceling from ublk_ctrl_start_recovery() to ublk_ctrl_end_recovery(), when IO handling can be recovered completely. Then blk_mq_quiesce_queue() and blk_mq_unquiesce_queue() are always used in same context. Signed-off-by: Ming Lei <ming.lei@redhat.com> Reviewed-by: Uday Shankar <ushankar@purestorage.com> Link: https://lore.kernel.org/r/20250416035444.99569-4-ming.lei@redhat.com Signed-off-by: Jens Axboe <axboe@kernel.dk> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions