From: Chandrakanth Patil <chandrakanth.patil@broadcom.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org,
Kashyap Desai <kashyap.desai@broadcom.com>,
Sumit Saxena <sumit.saxena@broadcom.com>,
Kiran Kumar Kasturi <kiran-kumar.kasturi@broadcom.com>,
Sankar Patra <sankar.patra@broadcom.com>,
Sasikumar PC <sasikumar.pc@broadcom.com>,
Shivasharan Srikanteshwara
<shivasharan.srikanteshwara@broadcom.com>,
Anand Lodnoor <anand.lodnoor@broadcom.com>
Subject: RE: [PATCH] megaraid_sas: change sdev queue depth max vs optimal
Date: Thu, 8 Aug 2019 22:56:56 +0530 [thread overview]
Message-ID: <06139ab3efab799a9d3148b1f04847b0@mail.gmail.com> (raw)
In-Reply-To: <yq1zhkke9c8.fsf@oracle.com>
Martin,
The firmware provided queue depth provides optimum performance in most of
the cases/workloads. And this patch provides the option to the user to go
with max queue_depth or with optimum queue_depth.
-Chandrakanth
-----Original Message-----
From: Martin K. Petersen [mailto:martin.petersen@oracle.com]
Sent: Thursday, August 8, 2019 6:56 AM
To: Chandrakanth Patil <chandrakanth.patil@broadcom.com>
Cc: linux-scsi@vger.kernel.org; kashyap.desai@broadcom.com;
sumit.saxena@broadcom.com; kiran-kumar.kasturi@broadcom.com;
sankar.patra@broadcom.com; sasikumar.pc@broadcom.com;
shivasharan.srikanteshwara@broadcom.com; anand.lodnoor@broadcom.com
Subject: Re: [PATCH] megaraid_sas: change sdev queue depth max vs optimal
Chandrakanth,
> This patch provides the module parameter and sysfs interface to switch
> between the firmware provided (optimal) queue depth and controller
> queue depth (can_queue).
This smells a bit like a don't-be-broken flag.
Why isn't the firmware-provided value optimal?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-08-08 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190726073214.23820-1-chandrakanth.patil@broadcom.com>
2019-08-08 1:26 ` [PATCH] megaraid_sas: change sdev queue depth max vs optimal Martin K. Petersen
2019-08-08 17:26 ` Chandrakanth Patil [this message]
2019-08-13 1:52 ` Martin K. Petersen
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=06139ab3efab799a9d3148b1f04847b0@mail.gmail.com \
--to=chandrakanth.patil@broadcom.com \
--cc=anand.lodnoor@broadcom.com \
--cc=kashyap.desai@broadcom.com \
--cc=kiran-kumar.kasturi@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sankar.patra@broadcom.com \
--cc=sasikumar.pc@broadcom.com \
--cc=shivasharan.srikanteshwara@broadcom.com \
--cc=sumit.saxena@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.