Hi,
On arm and ppc64, 'maxcpus=1' is required for kdump kernel,
see `Documentation/admin-guide/kdump/kdump.rst`, so num_possible_cpus()
still returns all CPUs because 'maxcpus=1' just bring up one single
cpu core during booting.
blk-mq sees single queue in kdump kernel, and in driver's viewpoint
there are still multiple queues, this inconsistency causes driver to apply
wrong queue mapping for handling IO, and IO timeout is triggered.
This issue is only triggered on managed irq in case of multiple hw
queues. Some drivers takes online cpus into account for nr_hw_queues,
and don't have such issue, such as nvme rdma/tcp.
Meantime, single queue makes much less resource utilization, and reduce
risk of kernel failure.
Thanks,
Ming
Ming Lei (8):
blk-mq: add blk_mq_max_nr_hw_queues()
nvme-pci: use blk_mq_max_nr_hw_queues() to calculate io queues
scsi: lpfc: use blk_mq_max_nr_hw_queues() to calculate io vectors
scsi: hisi: take blk_mq_max_nr_hw_queues() into account for
calculating io vectors
scsi: mpi3mr: take blk_mq_max_nr_hw_queues() into account for
calculating io vectors
scsi: megaraid: take blk_mq_max_nr_hw_queues() into account for
calculating io vectors
scsi: mpt3sas: take blk_mq_max_nr_hw_queues() into account for
calculating io vectors
scsi: pm8001: take blk_mq_max_nr_hw_queues() into account for
calculating io vectors
block/blk-mq.c | 9 +++++++++
drivers/nvme/host/pci.c | 2 +-
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 3 +++
drivers/scsi/lpfc/lpfc_init.c | 1 +
drivers/scsi/megaraid/megaraid_sas_base.c | 6 +++++-
drivers/scsi/mpi3mr/mpi3mr_fw.c | 3 +++
drivers/scsi/mpt3sas/mpt3sas_base.c | 4 ++--
drivers/scsi/pm8001/pm8001_init.c | 4 +++-
include/linux/blk-mq.h | 1 +
9 files changed, 28 insertions(+), 5 deletions(-)
--
2.40.1
