From: Michael Reed <mdr@sgi.com>
To: Karandeep Chahal <kchahal@ddn.com>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
dillowda@ornl.gov, roland@kernel.org, sean.hefty@intel.com
Subject: Re: [PATCH 1/1] ib_srp: Infiniband srp fast failover patch.
Date: Tue, 29 May 2012 14:51:58 -0700 [thread overview]
Message-ID: <4FC544FE.3000204@sgi.com> (raw)
In-Reply-To: <4FC53AAA.3060203@ddn.com>
Did you subsequently reconnect the target and confirm appropriate behavior?
On 05/29/2012 02:07 PM, Karandeep Chahal wrote:
> Subject: [PATCH] Infiniband srp fast failover patch. Currently ib_srp does
> not do anything on receiving a DREQ from the target, it
> only sends a response back. Further it also does not
> monitor port (down) events. I have patched srp to remove
> scsi devices when a port down event is received or if the
> target sends a DREQ. Currently even though the target
> notifies the initiator of its intentions of going away, the
> initiator ignores that information. Later the initiator
> gets upset when the devices "suddenly" disappear resulting
> in srp initiating an error recovery process which takes a
> long time. This caused high failover latencies as compared
> to fibre channel. In my experiments with RHEL 6.0 and 6.2 I
> encountered failover time that exceeded 2 minutes and 20
> seconds (despite tweaking /etc/multipath.conf and
> /sys/block/<>/timeout). With this patch the failover takes
> 30 seconds. I have tested this patch with and without a
> switch.
>
> Yours, etc.
> Karan
>
next prev parent reply other threads:[~2012-05-29 21:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 21:07 [PATCH 1/1] ib_srp: Infiniband srp fast failover patch Karandeep Chahal
2012-05-29 21:51 ` Michael Reed [this message]
2012-05-29 22:27 ` Karandeep Chahal
[not found] ` <4FC54D62.3080003-LfVdkaOWEx8@public.gmane.org>
2012-05-29 22:53 ` Michael Reed
2012-05-29 22:53 ` Michael Reed
[not found] ` <4FC53AAA.3060203-LfVdkaOWEx8@public.gmane.org>
2012-05-30 5:06 ` David Dillow
2012-05-30 5:06 ` David Dillow
2012-05-30 14:39 ` Karandeep Chahal
[not found] ` <1338354377.2361.13.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
2012-11-12 23:10 ` Or Gerlitz
[not found] ` <CAJZOPZL0cj6Sb_xs7prV0k8HjWkELD7Y89Bxxp-xXnnGqxvXyg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-11-12 23:46 ` Karandeep Chahal
[not found] ` <50A18A3D.9070304-LfVdkaOWEx8@public.gmane.org>
2012-11-13 21:07 ` Or Gerlitz
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=4FC544FE.3000204@sgi.com \
--to=mdr@sgi.com \
--cc=dillowda@ornl.gov \
--cc=kchahal@ddn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=roland@kernel.org \
--cc=sean.hefty@intel.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.