public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Giridhar Malavali <giridhar.malavali@qlogic.com>,
	"lsf-pc@lists.linux-foundation.org"
	<lsf-pc@lists.linux-foundation.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC] [ATTEND] scsi_eh updates
Date: Tue, 21 Jan 2014 07:52:50 +0100	[thread overview]
Message-ID: <52DE1942.3090908@suse.de> (raw)
In-Reply-To: <D63B9804CB63AD4FAAD9660376956646470290B2@avmb2.qlogic.org>

On 01/20/2014 07:44 PM, Giridhar Malavali wrote:
> 
> 
> On 12/20/13 6:54 AM, "Hannes Reinecke" <hare@suse.de> wrote:
> 
[ .. ]
>>
>> As discussed during last year's LSF the SCSI error handler should be
>> updated to handle modern SCSI transports better.
>> While some patchsets are already merged, there are some issues which
>> are still open:
>> - Handling of requests during host reset:
>>  Do we need to keep hold of outstanding requests during host reset?
>>  Or is it save to return them prior to host reset?
>> - Check for transport status prior to sending TMFs.
>>  Task management functions typically need a working I_T nexus,
>>  so it does make sense to first check the transport status
>>  prior to attempting any TMFs
>> - Further steps for updating SCSI EH
>> As these are tricky issues which have possible repercussions on the
>> entire subsystem and LLDDs it'd be good to have a broader discussion
>> here.
> 
> +1
> 
> I would like to participate in this discussion to provide inputs from
> LLDDs.
> 
And I would _very_ much like to have participation from LLDD
vendors/providers; as part of the scsi_eh update I plan to introduce
a new callback 'eh_transport_reset'.
Which need to be implemented at the LLDD level.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
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

      parent reply	other threads:[~2014-01-21  6:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20 14:54 [LSF/MM TOPIC] [ATTEND] scsi_eh updates Hannes Reinecke
2014-01-15 23:12 ` Nicholas A. Bellinger
2014-01-20 12:55 ` Bart Van Assche
2014-01-20 18:44 ` Giridhar Malavali
2014-01-20 19:05   ` James Bottomley
2014-01-21  6:52   ` Hannes Reinecke [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=52DE1942.3090908@suse.de \
    --to=hare@suse.de \
    --cc=giridhar.malavali@qlogic.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.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