From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: hare@suse.de
Cc: linux-scsi@vger.kernel.org, Brian Bunker <brian@purestorage.com>,
Krishna Kant <krishna.kant@purestorage.com>
Subject: Re: [PATCH] scsi: scsh_dh_alua use the device timeout rather than a constant
Date: Thu, 19 Mar 2026 22:26:16 -0400 [thread overview]
Message-ID: <yq1se9vjl0l.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20260224010754.37001-1-brian@purestorage.com> (Brian Bunker's message of "Mon, 23 Feb 2026 17:07:54 -0800")
> Instead of using a constant for timeouts, use the timeout of the SCSI
> device itself. There are reaasons why someone might want to extend the
> SCSI timeout and having the constant out of sync can lead to early
> timeouts.
Hannes: Please opine...
--
Martin K. Petersen
next prev parent reply other threads:[~2026-03-20 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 1:07 [PATCH] scsi: scsh_dh_alua use the device timeout rather than a constant Brian Bunker
2026-03-20 2:26 ` Martin K. Petersen [this message]
2026-03-23 15:15 ` John Garry
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=yq1se9vjl0l.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=brian@purestorage.com \
--cc=hare@suse.de \
--cc=krishna.kant@purestorage.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