From: Shivasharan Srikanteshwara <shivasharan.srikanteshwara@broadcom.com>
To: Hannes Reinecke <hare@suse.de>, linux-scsi@vger.kernel.org
Cc: martin.petersen@oracle.com, thenzl@redhat.com,
jejb@linux.vnet.ibm.com,
Kashyap Desai <kashyap.desai@broadcom.com>,
Sumit Saxena <sumit.saxena@broadcom.com>,
hare@suse.com, hch@lst.de
Subject: RE: [PATCH 11/15] megaraid_sas: Set device queue_depth same as HBA can_queue value in scsi-mq mode
Date: Tue, 4 Jul 2017 12:52:21 +0530 [thread overview]
Message-ID: <a84688d6248fd1ddb6cb7f001a941936@mail.gmail.com> (raw)
In-Reply-To: <40da55a6-77c5-340d-17cd-fae3c6f4c097@suse.de>
> -----Original Message-----
> From: Hannes Reinecke [mailto:hare@suse.de]
> Sent: Friday, June 30, 2017 7:10 PM
> To: Shivasharan S; linux-scsi@vger.kernel.org
> Cc: martin.petersen@oracle.com; thenzl@redhat.com;
> jejb@linux.vnet.ibm.com; kashyap.desai@broadcom.com;
> sumit.saxena@broadcom.com; hare@suse.com; hch@lst.de
> Subject: Re: [PATCH 11/15] megaraid_sas: Set device queue_depth same as
> HBA
> can_queue value in scsi-mq mode
>
> On 06/30/2017 10:30 AM, Shivasharan S wrote:
> > Currently driver sets default queue_depth for VDs at 256 and JBODs
> > based on interface type, ie., for SAS JBOD QD will be 64, for SATA JBOD
> > QD will
> be 32.
> > During performance runs with scsi-mq enabled, we are seeing better
> > results by setting QD same as HBA queue_depth.
> >
> > Signed-off-by: Kashyap Desai <kashyap.desai@broadcom.com>
> > Signed-off-by: Shivasharan S <shivasharan.srikanteshwara@broadcom.com>
> > ---
> > drivers/scsi/megaraid/megaraid_sas_base.c | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/scsi/megaraid/megaraid_sas_base.c
> > b/drivers/scsi/megaraid/megaraid_sas_base.c
> > index 0230929..c200f1a 100644
> > --- a/drivers/scsi/megaraid/megaraid_sas_base.c
> > +++ b/drivers/scsi/megaraid/megaraid_sas_base.c
> > @@ -1891,7 +1891,8 @@ static void
> megasas_set_static_target_properties(struct scsi_device *sdev,
> > if (instance->nvme_page_size && max_io_size_kb)
> > megasas_set_nvme_device_properties(sdev, (max_io_size_kb
> << 10));
> >
> > - scsi_change_queue_depth(sdev, device_qd);
> > + if (!shost_use_blk_mq(sdev->host))
> > + scsi_change_queue_depth(sdev, device_qd);
> >
> > }
> >
> > @@ -5914,6 +5915,9 @@ static int megasas_io_attach(struct
> megasas_instance *instance)
> > host->max_lun = MEGASAS_MAX_LUN;
> > host->max_cmd_len = 16;
> >
> > + if (shost_use_blk_mq(host))
> > + host->cmd_per_lun = host->can_queue;
> > +
> > /*
> > * Notify the mid-layer about the new controller
> > */
> >
> Is this bit really necessary? It will be adjusted by the above hunk, would
> it not?
>
The default cmd_per_lun is now set to 256 (MEGASAS_DEFAULT_CMD_PER_LUN).
In the above snip, we are changing cmd_per_lun to be equal to HBA
queue_depth for multiqueue enabled case.
So any scsi_device getting configured with scsi-mq enabled will have
queue_depth
set to cmd_per_lun value.
The hunk in megasas_set_static_target_properties is to update
the queue_depth for non-mq case only based on value provided by firmware.
Thanks,
Shivasharan
> Cheers,
>
> Hannes
> --
> Dr. Hannes Reinecke Teamlead Storage & Networking
> hare@suse.de +49 911 74053 688
> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
> GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton HRB 21284
> (AG
> Nürnberg)
next prev parent reply other threads:[~2017-07-04 7:22 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 8:29 [PATCH 00/15] megaraid_sas: Updates for scsi-next Shivasharan S
2017-06-30 8:29 ` [PATCH 01/15] megaraid_sas: mismatch of allocated MFI frame size and length exposed in MFI MPT pass through command Shivasharan S
2017-06-30 13:23 ` Hannes Reinecke
2017-06-30 8:29 ` [PATCH 02/15] megaraid_sas: set minimum value of resetwaittime to be 1 secs Shivasharan S
2017-06-30 13:23 ` Hannes Reinecke
2017-06-30 8:29 ` [PATCH 03/15] megaraid_sas: Use synchronize_irq in target reset case Shivasharan S
2017-06-30 13:24 ` Hannes Reinecke
2017-06-30 8:29 ` [PATCH 04/15] megaraid_sas: Call megasas_complete_cmd_dpc_fusion every 1 second while there are pending commands Shivasharan S
2017-06-30 13:25 ` Hannes Reinecke
2017-07-04 7:05 ` Shivasharan Srikanteshwara
2017-06-30 8:29 ` [PATCH 05/15] megaraid_sas: Do not re-fire shutdown DCMD after OCR Shivasharan S
2017-06-30 13:30 ` Hannes Reinecke
2017-07-04 7:08 ` Shivasharan Srikanteshwara
2017-07-05 10:33 ` Shivasharan Srikanteshwara
2017-07-05 10:34 ` Hannes Reinecke
2017-06-30 8:30 ` [PATCH 06/15] megaraid_sas: Fix endianness issues in DCMD handling Shivasharan S
2017-06-30 13:34 ` Hannes Reinecke
2017-06-30 8:30 ` [PATCH 07/15] megaraid_sas: Check valid aen class range to avoid kernel panic Shivasharan S
2017-06-30 13:35 ` Hannes Reinecke
2017-06-30 8:30 ` [PATCH 08/15] megaraid_sas: Use SMID for Task abort case only Shivasharan S
2017-06-30 13:35 ` Hannes Reinecke
2017-06-30 8:30 ` [PATCH 09/15] megaraid_sas: use vmalloc for crash dump buffers and driver's local RAID map Shivasharan S
2017-06-30 13:36 ` Hannes Reinecke
2017-06-30 14:30 ` Tomas Henzl
2017-07-03 7:13 ` Shivasharan Srikanteshwara
2017-06-30 8:30 ` [PATCH 10/15] megaraid_sas: Return pended IOCTLs with cmd_status MFI_STAT_WRONG_STATE in case adapter is dead Shivasharan S
2017-06-30 13:37 ` Hannes Reinecke
2017-06-30 8:30 ` [PATCH 11/15] megaraid_sas: Set device queue_depth same as HBA can_queue value in scsi-mq mode Shivasharan S
2017-06-30 13:39 ` Hannes Reinecke
2017-07-04 7:22 ` Shivasharan Srikanteshwara [this message]
2017-06-30 8:30 ` [PATCH 12/15] megaraid_sas: replace internal FALSE/TRUE definitions with false/true Shivasharan S
2017-06-30 13:40 ` Hannes Reinecke
2017-06-30 8:30 ` [PATCH 13/15] megaraid_sas: modified few prints in OCR and IOC INIT path Shivasharan S
2017-06-30 13:40 ` Hannes Reinecke
2017-06-30 8:30 ` [PATCH 14/15] megaraid_sas: call megasas_dump_frame with correct IO frame size Shivasharan S
2017-06-30 13:41 ` Hannes Reinecke
2017-06-30 8:30 ` [PATCH 15/15] megaraid_sas: driver version upgrade Shivasharan S
2017-06-30 13:41 ` Hannes Reinecke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a84688d6248fd1ddb6cb7f001a941936@mail.gmail.com \
--to=shivasharan.srikanteshwara@broadcom.com \
--cc=hare@suse.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sumit.saxena@broadcom.com \
--cc=thenzl@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox