From: Andries Brouwer <aebr@win.tue.nl>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Jens Axboe <axboe@suse.de>,
Patrick Mansfield <patmans@us.ibm.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Don't retry SG_IO (REQ_BLOCK_PC) commands.
Date: Sun, 23 Nov 2003 00:00:15 +0100 [thread overview]
Message-ID: <20031122230015.GA2366@win.tue.nl> (raw)
In-Reply-To: <1069423949.1826.10.camel@mulgrave>
On Fri, Nov 21, 2003 at 08:12:29AM -0600, James Bottomley wrote:
> To be more specific:
>
> I think we need to divide the error types up into
>
> 1. retryable
> 2. fatal
>
> and to have at least two, possibly three sources
>
> 1. the transport
> 2. the device
> (3. the driver)
>
> so a medium error (say a read failure) is a fatal device error;
> something like a no connect would be a fatal transport error, etc.
Yes, the driver is a legitimate source of errors.
If the driver knows that a certain command is not supported
and returns an error condition, then retrying is meaningless.
The error is not necessarily fatal in the sense that the device
does not work, it works just fine, but this particular command
will never get any other reply.
It also happens that the driver needs to allocate memory for
some command. If the allocation fails, that may be a retryable
condition, but immediately retrying is counterproductive.
Andries
next prev parent reply other threads:[~2003-11-22 23:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 16:55 [PATCH] Don't retry SG_IO (REQ_BLOCK_PC) commands Patrick Mansfield
2003-11-20 18:15 ` Mike Anderson
2003-11-20 19:16 ` Jens Axboe
2003-11-20 21:51 ` Patrick Mansfield
2003-11-21 10:17 ` Jens Axboe
2003-11-21 12:48 ` James Bottomley
2003-11-21 14:12 ` James Bottomley
2003-11-22 23:00 ` Andries Brouwer [this message]
2003-11-21 16:26 ` Patrick Mansfield
2003-11-21 18:23 ` Jens Axboe
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=20031122230015.GA2366@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=James.Bottomley@steeleye.com \
--cc=axboe@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox