From: Boaz Harrosh <bharrosh@panasas.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: How many retries to allow?
Date: Sun, 28 Sep 2008 12:25:02 +0300 [thread overview]
Message-ID: <48DF4D6E.5060509@panasas.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0809251616260.2181-100000@iolanthe.rowland.org>
Alan Stern wrote:
> James and Boaz:
>
> Here's a question. Suppose a device returns NOT READY sense key
> repeatedly. How long should the request be retried before we give up?
> If we never give up then the request will never finish, so the caller
> will hang.
>
> Alan Stern
>
I always thought request->retries was for that. Perhaps I misunderstood.
I think there should be one user settable global counter that will limit
all retries of any kind.
Just my $0.017
Boaz
next prev parent reply other threads:[~2008-09-28 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 20:18 How many retries to allow? Alan Stern
2008-09-28 9:25 ` Boaz Harrosh [this message]
2008-09-28 15:44 ` Alan Stern
2008-09-28 16:16 ` Boaz Harrosh
2008-09-29 21:14 ` Alan Stern
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=48DF4D6E.5060509@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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