diff options
| author | Jianchao Wang <[email protected]> | 2018-08-21 07:15:03 +0000 |
|---|---|---|
| committer | Jens Axboe <[email protected]> | 2018-08-21 15:02:55 +0000 |
| commit | d48ece209f82c9ce07be942441b53d3fa3664936 (patch) | |
| tree | ddf957d9d4edf1915558bc528fee6696cc02f1ed /tools/perf/scripts/python/stat-cpi.py | |
| parent | block: remove duplicate initialization (diff) | |
| download | kernel-d48ece209f82c9ce07be942441b53d3fa3664936.tar.gz kernel-d48ece209f82c9ce07be942441b53d3fa3664936.zip | |
blk-mq: init hctx sched after update ctx and hctx mapping
Currently, when update nr_hw_queues, IO scheduler's init_hctx will
be invoked before the mapping between ctx and hctx is adapted
correctly by blk_mq_map_swqueue. The IO scheduler init_hctx (kyber)
may depend on this mapping and get wrong result and panic finally.
A simply way to fix this is that switch the IO scheduler to 'none'
before update the nr_hw_queues, and then switch it back after
update nr_hw_queues. blk_mq_sched_init_/exit_hctx are removed due
to nobody use them any more.
Signed-off-by: Jianchao Wang <[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