From: James Smart <jsmart2021@gmail.com>
To: Mike Christie <michael.christie@oracle.com>,
Muneendra <muneendra.kumar@broadcom.com>,
linux-scsi@vger.kernel.org, hare@suse.de
Cc: emilne@redhat.com, mkumar@redhat.com
Subject: Re: [PATCH v2 0/8] scsi: Support to handle Intermittent errors
Date: Fri, 2 Oct 2020 10:27:48 -0700 [thread overview]
Message-ID: <1ee1eeea-bb55-3630-a3a7-6222b6a20671@gmail.com> (raw)
In-Reply-To: <4a2ed7c2-48a9-60d0-d751-d06af7fa6750@oracle.com>
On 10/2/2020 10:01 AM, Mike Christie wrote:
> On 9/27/20 11:50 PM, Muneendra wrote:
>> This patch adds a support to prevent retries of all the pending/inflight
>> io's after an abort succeeds on a particular device when transport
>> connectivity to the device is encountering intermittent errors.
>>
>> Intermittent connectivity is a condition that can be detected by transport
>> fabric notifications. A service can monitor the ELS notifications and
>> take action on all the outstanding io's of a scsi device at that instant.
>>
>
> Is the service mentioned above a new daemon or is it integrated into
> something like multipathd?
>
> What does the part about monitoring ELS notifications mean? Is the
> service just doing something like a ELS ECHO, or is it able to watch
> the IO on the wire/card (like if you did tcpdump and watched iscsi/tcp
> traffic) or is it something completely different?
>
For the last part.... the FC drivers, when receiving FC FPIN ELS's are
calling a scsi transport routine with the FPIN payload. The transport
is pushing this as an "event" via netlink. An app bound to the local
address used by the scsi transport can receive the event and parse it.
This is a new daemon, specific to FC, which monitors for FPIN events,
parses the related topology devices, then interacts with sysfs and
possibly multipath based on what it's seeing from the fabric.
-- james
prev parent reply other threads:[~2020-10-02 17:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 4:50 [PATCH v2 0/8] scsi: Support to handle Intermittent errors Muneendra
2020-09-28 4:50 ` [PATCH v2 1/8] scsi: Added a new definition in scsi_cmnd.h Muneendra
2020-09-30 9:17 ` Hannes Reinecke
2020-09-28 4:50 ` [PATCH v2 2/8] scsi: Added a new error code in scsi.h Muneendra
2020-09-30 9:17 ` Hannes Reinecke
2020-09-28 4:50 ` [PATCH v2 3/8] scsi: Clear state bit SCMD_NORETRIES_ABORT of scsi_cmd before start request Muneendra
2020-09-30 9:19 ` Hannes Reinecke
2020-09-28 4:50 ` [PATCH v2 4/8] scsi: No retries on abort success Muneendra
2020-09-30 9:27 ` Hannes Reinecke
2020-09-28 4:50 ` [PATCH v2 5/8] scsi: Added routine to set/clear SCMD_NORETRIES_ABORT bit for outstanding io on scsi_dev Muneendra
2020-09-30 9:26 ` Hannes Reinecke
2020-09-28 4:50 ` [PATCH v2 6/8] scsi_transport_fc: Added a new rport state FC_PORTSTATE_MARGINAL Muneendra
2020-09-30 9:30 ` Hannes Reinecke
2020-09-28 4:50 ` [PATCH v2 7/8] scsi_transport_fc: Added a new sysfs attribute port_state Muneendra
2020-09-30 9:33 ` Hannes Reinecke
2020-10-01 13:13 ` Muneendra Kumar M
2020-10-05 9:18 ` Muneendra Kumar M
2020-10-05 9:29 ` Hannes Reinecke
2020-10-07 7:14 ` Muneendra Kumar M
2020-10-02 16:26 ` Benjamin Block
2020-10-05 6:49 ` Hannes Reinecke
2020-10-05 8:41 ` Benjamin Block
2020-09-28 4:50 ` [PATCH v2 8/8] lpfc: Added support to handle marginal state Muneendra
2020-09-30 9:36 ` Hannes Reinecke
2020-09-30 11:33 ` Muneendra Kumar M
2020-09-30 11:50 ` Hannes Reinecke
2020-10-01 8:59 ` Muneendra Kumar M
2020-10-02 17:01 ` [PATCH v2 0/8] scsi: Support to handle Intermittent errors Mike Christie
2020-10-02 17:27 ` James Smart [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=1ee1eeea-bb55-3630-a3a7-6222b6a20671@gmail.com \
--to=jsmart2021@gmail.com \
--cc=emilne@redhat.com \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=michael.christie@oracle.com \
--cc=mkumar@redhat.com \
--cc=muneendra.kumar@broadcom.com \
/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.