From: Mike Christie <michaelc@cs.wisc.edu>
To: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/4] scsi: add transport host byte errors
Date: Wed, 14 Mar 2007 15:11:12 -0500 [thread overview]
Message-ID: <45F856E0.3000808@cs.wisc.edu> (raw)
In-Reply-To: <11739019703157-git-send-email-michaelc@cs.wisc.edu>
michaelc@cs.wisc.edu wrote:
> The following patches attempt unify what upper layers will see drivers
> like multipath can make a good guess. This relies on drivers being
Oops, I mean to say with the patches upper layers like multipath will
see common behavior from LLDs hooked into transport classes. If the
class/LLD can block a rport/session and recover within
fast_io_fail_tmo/replacement_timeout seconds then multipath would not
see the problem. We will not have some drivers returning errors upwards
and some not and some drivers holding onto errors for until the device
is removed.
next prev parent reply other threads:[~2007-03-14 20:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 19:52 RFC: add transport host byte values and common failure behavior michaelc
2007-03-14 19:52 ` [PATCH 1/4] iscsi class, qla4xxx and libiscsi: export iscsi session state in sysfs michaelc
2007-03-14 19:52 ` [PATCH 2/4] scsi: add transport host byte errors michaelc
2007-03-14 19:52 ` [PATCH 3/4] iscsi class, libiscsi and qla4xxx: convert to new transport host byte values michaelc
2007-03-14 19:52 ` [PATCH 4/4] fc class: use " michaelc
2007-03-14 20:11 ` Mike Christie [this message]
2007-03-14 21:14 ` [PATCH 2/4] scsi: add transport host byte errors Mike Christie
2007-03-15 13:41 ` [PATCH 4/4] fc class: use transport host byte values James Smart
2007-03-15 14:26 ` Mike Christie
2007-03-15 14:45 ` James Smart
2007-03-15 13:20 ` [PATCH 2/4] scsi: add transport host byte errors James Smart
2007-03-15 14:52 ` Mike Christie
2007-03-15 16:33 ` James Smart
2007-03-15 12:58 ` [PATCH 1/4] iscsi class, qla4xxx and libiscsi: export iscsi session state in sysfs James Smart
2007-03-15 14:20 ` Mike Christie
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=45F856E0.3000808@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.