public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Karandeep Chahal <kchahal@ddn.com>
To: David Dillow <dillowda@ornl.gov>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"roland@kernel.org" <roland@kernel.org>,
	"sean.hefty@intel.com" <sean.hefty@intel.com>
Subject: Re: [PATCH 1/1] ib_srp: Infiniband srp fast failover patch.
Date: Wed, 30 May 2012 10:39:46 -0400	[thread overview]
Message-ID: <4FC63132.60609@ddn.com> (raw)
In-Reply-To: <1338354377.2361.13.camel@obelisk.thedillows.org>

Hi Dave,

As long as we get faster failover I am happy with Bart's patch.

Currently when I run IO to several luns over multipath and the preferred 
path goes down, the system hangs until the IO fails over. Even ssh'ing 
into the systems take 20-30 seconds. I *suspect* that is because IO is 
being queued up somewhere which brings the whole system to its knees.

Thank you for looking at the patch.

Thanks
Karan

On 05/30/2012 01:06 AM, David Dillow wrote:
> On Tue, 2012-05-29 at 17:07 -0400, Karandeep Chahal wrote:
>> Subject: [PATCH] Infiniband srp fast failover patch.
> This conflicts with Bart's patches to improve failover; it will be much
> better to use his approach to block the target rather than remove it
> wholesale -- we could have lost connectivity as a transient and may get
> it back quickly if someone grabbed the wrong cable, etc.
>
> Also, we should only kill the one target on DREQ, and we already have a
> pointer to it from the CM context -- no need to search.
>
> It is a good idea to hook into the event mechanism; this is something
> I've long wanted to incorporate (as Vu did in OFED). I'm looking at
> getting Bart's series to a point I can merge it, and I'll pull in your
> ideas -- with credit -- there.
>
> Thanks,

  reply	other threads:[~2012-05-30 14:39 UTC|newest]

Thread overview: 9+ 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
2012-05-29 22:27   ` Karandeep Chahal
     [not found]     ` <4FC54D62.3080003-LfVdkaOWEx8@public.gmane.org>
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 14:39     ` Karandeep Chahal [this message]
     [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=4FC63132.60609@ddn.com \
    --to=kchahal@ddn.com \
    --cc=dillowda@ornl.gov \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox