From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: lduncan@suse.com
Cc: Gabriel Krisman Bertazi <krisman@collabora.com>,
Khazhismel Kumykov <khazhy@google.com>,
Chris Leech <cleech@redhat.com>,
jejb@linux.ibm.com,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"'Khazhismel Kumykov' via open-iscsi"
<open-iscsi@googlegroups.com>,
linux-scsi@vger.kernel.org, Bharath Ravi <rbharath@google.com>,
kernel@collabora.com, Mike Christie <mchristi@redhat.com>,
Bart Van Assche <bvanassche@acm.org>,
Dave Clausen <dclausen@google.com>, Nick Black <nlb@google.com>,
Vaibhav Nagarnaik <vnagarnaik@google.com>,
Anatol Pomazau <anatol@google.com>,
Tahsin Erdogan <tahsin@google.com>,
Frank Mayhar <fmayhar@google.com>, Junho Ryu <jayr@google.com>
Subject: Re: [PATCH v4] iscsi: Perform connection failure entirely in kernel space
Date: Wed, 15 Jan 2020 22:52:21 -0500 [thread overview]
Message-ID: <yq1tv4wnjm2.fsf@oracle.com> (raw)
In-Reply-To: <85r20g2vfw.fsf_-_@collabora.com> (Gabriel Krisman Bertazi's message of "Fri, 03 Jan 2020 14:26:11 -0500")
> Please consider the v4 below with the lock added.
Lee: Please re-review this given the code change.
> From: Bharath Ravi <rbharath@google.com>
>
> Connection failure processing depends on a daemon being present to (at
> least) stop the connection and start recovery. This is a problem on a
> multipath scenario, where if the daemon failed for whatever reason, the
> SCSI path is never marked as down, multipath won't perform the
> failover and IO to the device will be forever waiting for that
> connection to come back.
>
> This patch performs the connection failure entirely inside the kernel.
> This way, the failover can happen and pending IO can continue even if
> the daemon is dead. Once the daemon comes alive again, it can execute
> recovery procedures if applicable.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2020-01-16 3:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 20:47 [PATCH v3] iscsi: Perform connection failure entirely in kernel space Gabriel Krisman Bertazi
2020-01-01 18:45 ` Lee Duncan
2020-01-02 17:07 ` Khazhismel Kumykov
2020-01-02 18:13 ` Gabriel Krisman Bertazi
2020-01-02 18:24 ` Khazhismel Kumykov
2020-01-03 19:26 ` [PATCH v4] " Gabriel Krisman Bertazi
2020-01-03 19:40 ` Khazhismel Kumykov
2020-01-16 3:52 ` Martin K. Petersen [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=yq1tv4wnjm2.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=anatol@google.com \
--cc=bvanassche@acm.org \
--cc=cleech@redhat.com \
--cc=dclausen@google.com \
--cc=fmayhar@google.com \
--cc=jayr@google.com \
--cc=jejb@linux.ibm.com \
--cc=kernel@collabora.com \
--cc=khazhy@google.com \
--cc=krisman@collabora.com \
--cc=lduncan@suse.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mchristi@redhat.com \
--cc=nlb@google.com \
--cc=open-iscsi@googlegroups.com \
--cc=rbharath@google.com \
--cc=tahsin@google.com \
--cc=vnagarnaik@google.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.