From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Chandrakanth Patil <chandrakanth.patil@broadcom.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
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: Mon, 12 Aug 2019 21:52:57 -0400 [thread overview]
Message-ID: <yq1h86l96h2.fsf@oracle.com> (raw)
In-Reply-To: <06139ab3efab799a9d3148b1f04847b0@mail.gmail.com> (Chandrakanth Patil's message of "Thu, 8 Aug 2019 22:56:56 +0530")
Chandrakanth,
> 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.
I guess I'm just objecting to the notion that something is being
described as "optimum" when it clearly isn't.
Applied to 5.4/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2019-08-13 1:53 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
2019-08-13 1:52 ` Martin K. Petersen [this message]
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=yq1h86l96h2.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=anand.lodnoor@broadcom.com \
--cc=chandrakanth.patil@broadcom.com \
--cc=kashyap.desai@broadcom.com \
--cc=kiran-kumar.kasturi@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--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.