blk-mq: don't change nr_hw_queues and nr_maps for kdump kernel
authorMing Lei <ming.lei@redhat.com>
Wed, 28 Feb 2024 04:08:57 +0000 (12:08 +0800)
committerJens Axboe <axboe@kernel.dk>
Wed, 28 Feb 2024 14:22:06 +0000 (07:22 -0700)
commitec30b461f3d067bd322a6c3a6c5105746ed9bf14
treef6e65bf1c333892dca5d08e61c943067fcc1d873
parentfb5d1d389c9e78d68f1f71f926d6251017579f5b
blk-mq: don't change nr_hw_queues and nr_maps for kdump kernel

For most of ARCHs, 'nr_cpus=1' is passed for kdump kernel, so
nr_hw_queues for each mapping is supposed to be 1 already.

More importantly, this way may cause trouble for driver, because blk-mq and
driver see different queue mapping since driver should setup hardware
queue setting before calling into allocating blk-mq tagset.

So not overriding nr_hw_queues and nr_maps for kdump kernel.

Cc: Wen Xiong <wenxiong@us.ibm.com>
Signed-off-by: Ming Lei <ming.lei@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Link: https://lore.kernel.org/r/20240228040857.306483-1-ming.lei@redhat.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
block/blk-mq.c