diff options
author | Ming Lei <[email protected]> | 2018-04-08 17:48:07 +0800 |
---|---|---|
committer | Jens Axboe <[email protected]> | 2018-04-10 08:38:46 -0600 |
commit | a1c735fb790745f94a359df45c11df4a69760389 (patch) | |
tree | 0ec9fdf86086885756ceecadb154c44eec8973bf /tools/perf/scripts/python/export-to-postgresql.py | |
parent | bdac616db9bbadb90b7d6a406144571015e138f7 (diff) |
blk-mq: make sure that correct hctx->next_cpu is set
From commit 20e4d81393196 (blk-mq: simplify queue mapping & schedule
with each possisble CPU), one hctx can be mapped from all offline CPUs,
then hctx->next_cpu can be set as wrong.
This patch fixes this issue by making hctx->next_cpu pointing to the
first CPU in hctx->cpumask if all CPUs in hctx->cpumask are offline.
Cc: Stefan Haberland <[email protected]>
Tested-by: Christian Borntraeger <[email protected]>
Reviewed-by: Christoph Hellwig <[email protected]>
Reviewed-by: Sagi Grimberg <[email protected]>
Fixes: 20e4d81393196 ("blk-mq: simplify queue mapping & schedule with each possisble CPU")
Cc: [email protected]
Signed-off-by: Ming Lei <[email protected]>
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions