All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kashyap Desai <kashyap.desai@avagotech.com>
To: hare@suse.de, linux-scsi@vger.kernel.org
Subject: Scsi Error handling query
Date: Thu, 26 Mar 2015 19:08:54 +0530	[thread overview]
Message-ID: <5d00e10b067fd4d0fb82ecdec18dd325@mail.gmail.com> (raw)

Hi Hannes,

I was going through one of the slide posted at below link.

http://events.linuxfoundation.org/sites/events/files/slides/SCSI-EH.pdf

Slide #59 has below data. I was trying to correlate with latest upstream
code, but do not understand few things. Does Linux handle blocking I/O to
the device and target before it actually start legacy EH recovery ? Also,
how does linux scsi stack achieve task set abort ?

Proposed SCSI EH strategy
• Send command aborts after timeout
• EH Recovery starts:
‒ Block I/O to the device
       ‒ Issue 'Task Set Abort'
‒ Block I/O to the target
       ‒ Issue I_T Nexus Reset
       ‒ Complete outstanding command on success
‒ Engage current EH strategy
       ‒ LUN Reset, Target Reset etc


Thanks, Kashyap
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2015-03-26 13:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 13:38 Kashyap Desai [this message]
2015-03-26 15:57 ` Scsi Error handling query Hannes Reinecke
2015-03-26 18:43   ` Kashyap Desai
2015-03-27 16:02     ` Hannes Reinecke
2015-03-30 11:45       ` Kashyap Desai
2015-03-30 15:12         ` Hannes Reinecke
2015-03-31 13:33           ` Kashyap Desai

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=5d00e10b067fd4d0fb82ecdec18dd325@mail.gmail.com \
    --to=kashyap.desai@avagotech.com \
    --cc=hare@suse.de \
    --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.