On 07/12/2016 04:02 PM, [email protected] wrote:
> From: Wen Xiong <[email protected]>
>
> Add scsi multi-queue support in ipr driver. This feature
> is enabled by setting ipr_use_blk_mq=1 when loading ipr
> module and scsi blk-mq is enabled in the kernel.
>
> Signed-off-by: Wen Xiong <[email protected]>
> ---
> drivers/scsi/ipr.c | 16 ++++++++++++++--
> drivers/scsi/ipr.h | 1 +
> 2 files changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/scsi/ipr.c b/drivers/scsi/ipr.c
> index 1f539c2..21b6da6 100644
> --- a/drivers/scsi/ipr.c
> +++ b/drivers/scsi/ipr.c
> @@ -100,6 +100,7 @@ static unsigned int ipr_max_devs = IPR_DEFAULT_SIS64_DEVS;
> static unsigned int ipr_dual_ioa_raid = 1;
> static unsigned int ipr_number_of_msix = 16;
> static unsigned int ipr_fast_reboot;
> +static unsigned int ipr_use_blk_mq = 0;
No need to initialize a static to 0. Can you be sure to run
scripts/checkpatch.pl
in future?
> @@ -6329,7 +6333,12 @@ static int ipr_queuecommand(struct Scsi_Host *shost,
> return rc;
> }
>
> - hrrq_id = ipr_get_hrrq_index(ioa_cfg);
> + if (ioa_cfg->use_blk_mq && shost_use_blk_mq(scsi_cmd->device->host)) {
> + tag = blk_mq_unique_tag(scsi_cmd->request);
> + hrrq_id = blk_mq_unique_tag_to_hwq(tag);
> + } else
> + hrrq_id = ipr_get_hrrq_index(ioa_cfg);
> +
> hrrq = &ioa_cfg->hrrq[hrrq_id];
>
> spin_lock_irqsave(hrrq->lock, hrrq_flags);
> @@ -10144,6 +10153,8 @@ static int ipr_probe_ioa(struct pci_dev *pdev,
> (unsigned int)num_online_cpus(),
> (unsigned int)IPR_MAX_HRRQ_NUM);
>
> + host->nr_hw_queues = ioa_cfg->hrrq_num;
Prior to this patch we reserved HRRQ 0 for error interrupts. This changes that
to use it also for normal I/O interrupts. One side effect of this is that we
can now no longer use iopoll for HRRQ 0. It would be nice to not change this
behavior and keep using HRRQ 0 for errors only, since we have an MMIO read
in that path we wanted to avoid in the normal I/O path.
I think if we just change the line above to:
host->nr_hw_queues = ioa_cfg->hrrq_num - 1;
Then this should resolve this. Can you verify this doesn't break anything?
Thanks,
Brian
--
Brian King
Power Linux I/O
IBM Linux Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
