From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: James Smart <jsmart2021@gmail.com>
Cc: linux-scsi@vger.kernel.org, bvanassche@acm.org
Subject: Re: [PATCH v3 0/3] scsi: add attribute to set lun queue depth on all luns on shost
Date: Tue, 04 Feb 2020 21:56:16 -0500 [thread overview]
Message-ID: <yq1v9olzqr3.fsf@oracle.com> (raw)
In-Reply-To: <20200124230115.14562-1-jsmart2021@gmail.com> (James Smart's message of "Fri, 24 Jan 2020 15:01:12 -0800")
James,
> There has been a desire to set the lun queue depth on all luns on an
> shost. Today that is done by an external script looping through
> discovered sdevs and set an sdev attribute. The desire is to have a
> single shost attribute that performs this work removing the
> requirement for scripting.
I'd like you to elaborate a bit on this.
- Why is scripting or adding a udev rule inadequate?
- Why is there a requirement to statically clamp the queue depth
instead of letting the device manage it?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2020-02-05 2:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 23:01 [PATCH v3 0/3] scsi: add attribute to set lun queue depth on all luns on shost James Smart
2020-01-24 23:01 ` [PATCH v3 1/3] scsi: refactor sdev lun queue depth setting via sysfs James Smart
2020-01-25 5:54 ` Bart Van Assche
2020-01-24 23:01 ` [PATCH v3 2/3] scsi: add shost helper to set max queue depth on all of its devices James Smart
2020-01-25 5:53 ` Bart Van Assche
2020-01-24 23:01 ` [PATCH v3 3/3] scsi: add shost attribute to set max queue depth on all devices on the shost James Smart
2020-01-25 5:51 ` Bart Van Assche
2020-02-05 2:56 ` Martin K. Petersen [this message]
2020-02-05 18:57 ` [PATCH v3 0/3] scsi: add attribute to set lun queue depth on all luns on shost James Smart
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=yq1v9olzqr3.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bvanassche@acm.org \
--cc=jsmart2021@gmail.com \
--cc=linux-scsi@vger.kernel.org \
/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