aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/stat-cpi.py
diff options
context:
space:
mode:
authorJianchao Wang <[email protected]>2018-08-21 07:15:04 +0000
committerJens Axboe <[email protected]>2018-08-21 15:02:56 +0000
commitf5bbbbe4d63577026f908a809f22f5fd5a90ea1f (patch)
treea6d8a1e7329b4160285b79a0565a45b53a2809f6 /tools/perf/scripts/python/stat-cpi.py
parentblk-mq: init hctx sched after update ctx and hctx mapping (diff)
downloadkernel-f5bbbbe4d63577026f908a809f22f5fd5a90ea1f.tar.gz
kernel-f5bbbbe4d63577026f908a809f22f5fd5a90ea1f.zip
blk-mq: sync the update nr_hw_queues with blk_mq_queue_tag_busy_iter
For blk-mq, part_in_flight/rw will invoke blk_mq_in_flight/rw to account the inflight requests. It will access the queue_hw_ctx and nr_hw_queues w/o any protection. When updating nr_hw_queues and blk_mq_in_flight/rw occur concurrently, panic comes up. Before update nr_hw_queues, the q will be frozen. So we could use q_usage_counter to avoid the race. percpu_ref_is_zero is used here so that we will not miss any in-flight request. The access to nr_hw_queues and queue_hw_ctx in blk_mq_queue_tag_busy_iter are under rcu critical section, __blk_mq_update_nr_hw_queues could use synchronize_rcu to ensure the zeroed q_usage_counter to be globally visible. Signed-off-by: Jianchao Wang <[email protected]> Reviewed-by: Ming Lei <[email protected]> Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/stat-cpi.py')
0 files changed, 0 insertions, 0 deletions