linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Hagan, Steve" <Steve.Hagan@lsi.com>
Cc: "Moore, Eric" <Eric.Moore@lsi.com>,
	Mike Christie <michaelc@cs.wisc.edu>,
	linux-scsi@vger.kernel.org, james.smart@emulex.com,
	andrew.vasquez@qlogic.com, christof.schmitt@de.ibm.com,
	mp3@de.ibm.com, rmk@arm.linux.org.uk, matthew@wil.cx, "Rivera,
	Peter" <Peter.Rivera@lsi.com>,
	"Prakash, Sathya" <Sathya.Prakash@lsi.com>
Subject: RE: scsi: fix target reset handling
Date: Tue, 04 Mar 2008 12:00:34 -0600	[thread overview]
Message-ID: <1204653634.3091.47.camel@localhost.localdomain> (raw)
In-Reply-To: <61DA31637BAF774FB13AC59B6381C080A9CFC1@NAMAIL4.ad.lsil.com>

On Tue, 2008-03-04 at 10:40 -0700, Hagan, Steve wrote:
> Windows (StorPort drivers) supports LUN, target, and bus resets in a
> hierarchical fashion.  If an I/O times out, Storport will issue a LUN
> reset first.  If that fails, it will escalate to a target reset.  If
> that fails, it will escalate to a bus reset.
> 
> What does "fail" mean?

Fail means the driver was unable to perform the action.  i.e failure of
a LUN reset means we couldn't get the TMF out.

>   If the TM request returns with a non-success
> status, or if there are outstanding I/O's for the scope of the reset
> remaining after we receive the TM reply, then the reset is considered
> failed.

Outstanding I/O is a dubious point.  Your driver could have outstanding
I/O for the LUN after a LUN reset, but if the device correctly executed
it, it will have cleared its queue.

>   Our miniport driver will return error status back to Storport
> and it will escalate to the next level of reset.  A bus reset cannot be
> failed back to Storport.  If a bus reset fails (as above) then the only
> recourse if for the miniport to do a hard reset of the adapter and
> return all outstanding I/O's with reset status.

That's pretty much what the default error handler does.

James



      reply	other threads:[~2008-03-04 18:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-01  0:25 scsi: fix target reset handling michaelc
2008-03-01  0:25 ` [PATCH 1/5] scsi_error: add target reset handler michaelc
2008-03-01  0:25   ` [PATCH 2/5] qla4xxx: Add target reset functionality michaelc
2008-03-01  0:25     ` [PATCH 3/5] Convert qla2xxx, mpt, arm, sym, a100u2w, qla1280 to target reset handler michaelc
2008-03-01  0:25       ` [PATCH 4/5] lpfc: convert lpfc to use " michaelc
2008-03-01  0:25         ` [PATCH 5/5] zfcp: convert zfcp to use target reset and device " michaelc
2008-03-01 13:34           ` Christof Schmitt
2008-03-01 13:36           ` [PATCH] " Christof Schmitt
2008-03-02  9:09             ` Mike Christie
2008-03-03  9:39             ` Heiko Carstens
2008-03-03 10:12               ` Christof Schmitt
2008-03-03 10:19                 ` Christof Schmitt
2008-03-03 10:40                   ` Russell King
2008-03-03 11:18                     ` Christof Schmitt
2008-03-03 11:19                     ` Christof Schmitt
2008-04-21 20:43         ` [PATCH 4/5] lpfc: convert lpfc to use target " James Smart
2008-03-05  5:08       ` [PATCH 3/5] Convert qla2xxx, mpt, arm, sym, a100u2w, qla1280 to " Andrew Vasquez
2008-03-05 17:11         ` Mike Christie
2008-03-01  0:27 ` scsi: fix target reset handling Mike Christie
2008-03-03 17:06 ` Moore, Eric
2008-03-04 15:21   ` Mike Christie
2008-03-04 17:34     ` Moore, Eric
2008-03-04 17:40       ` Hagan, Steve
2008-03-04 18:00         ` James Bottomley [this message]

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=1204653634.3091.47.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=Eric.Moore@lsi.com \
    --cc=Peter.Rivera@lsi.com \
    --cc=Sathya.Prakash@lsi.com \
    --cc=Steve.Hagan@lsi.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=christof.schmitt@de.ibm.com \
    --cc=james.smart@emulex.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=michaelc@cs.wisc.edu \
    --cc=mp3@de.ibm.com \
    --cc=rmk@arm.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).