From: Jeremy Linton <jlinton@tributary.com>
To: "Elliott, Robert (Server Storage)" <Elliott@hp.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Use a more selective error recovery strategy based on device capabilities
Date: Tue, 12 Feb 2013 16:00:15 -0600 [thread overview]
Message-ID: <511ABB6F.1000700@tributary.com> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B402950D4811C@G4W3304.americas.hpqcorp.net>
On 2/12/2013 2:57 PM, Elliott, Robert (Server Storage) wrote:
> Ideally the device driver for the SCSI initiator port would report those
> attributes, and higher level code would combine them with support
> information from the device server (REPORT SUPPORTED TMF command, REPORT
> SUPPORTED OPCODES command, etc.) to decide what is supported.
Well, for the eh_xxx_handler functions, that is basically what happens now.
The host driver can fail to set a callback for the eh_xxx_handlers if it
doesn't support the operation. At that point, even if the target device
supports a function (say target reset) if the host driver doesn't, then the
target reset will be skipped.
Of course, a number of the drivers define functions their underlying
protocol's don't support. For example, bus reset on fibre channel. Which I
personally believe is an error.
next prev parent reply other threads:[~2013-02-12 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 18:19 [PATCH] Use a more selective error recovery strategy based on device capabilities Jeremy Linton
2013-02-12 20:57 ` Elliott, Robert (Server Storage)
2013-02-12 22:00 ` Jeremy Linton [this message]
2013-02-13 13:06 ` Hannes Reinecke
2013-02-13 15:46 ` Jeremy Linton
2013-02-14 2:43 ` Michael Christie
2013-02-14 20:57 ` Jeremy Linton
2013-02-14 23:42 ` Elliott, Robert (Server Storage)
2013-02-15 15:17 ` Jeremy Linton
2013-02-15 7:17 ` Hannes Reinecke
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=511ABB6F.1000700@tributary.com \
--to=jlinton@tributary.com \
--cc=Elliott@hp.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