diff options
author | 2022-02-17 14:42:47 +0800 | |
---|---|---|
committer | 2022-02-22 06:59:09 -0700 | |
commit | 86d7331299fda7634b11c1b7c911432679d525a5 (patch) | |
tree | d90ad24e37936eb34fefb27935cc9fedf2e93ce3 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | block, bfq: don't move oom_bfqq (diff) | |
download | wireguard-linux-86d7331299fda7634b11c1b7c911432679d525a5.tar.xz wireguard-linux-86d7331299fda7634b11c1b7c911432679d525a5.zip |
block: update io_ticks when io hang
When the inflight IOs are slow and no new IOs are issued, we expect
iostat could manifest the IO hang problem. However after
commit 5b18b5a73760 ("block: delete part_round_stats and switch to less
precise counting"), io_tick and time_in_queue will not be updated until
the end of IO, and the avgqu-sz and %util columns of iostat will be zero.
Because it has using stat.nsecs accumulation to express time_in_queue
which is not suitable to change, and may %util will express the status
better when io hang occur. To fix io_ticks, we use update_io_ticks and
inflight to update io_ticks when diskstats_show and part_stat_show
been called.
Fixes: 5b18b5a73760 ("block: delete part_round_stats and switch to less precise counting")
Signed-off-by: Zhang Wensheng <zhangwensheng5@huawei.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Link: https://lore.kernel.org/r/20220217064247.4041435-1-zhangwensheng5@huawei.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions