linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-rmda <linux-rdma@vger.kernel.org>,
	Roland Dreier <roland@purestorage.com>, Vu Pham <vu@mellanox.com>,
	David Dillow <dillowda@ornl.gov>,
	James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [RFC] ib_srpt: initial .40-rc1 drivers/infiniband/ulp/srpt merge
Date: Thu, 19 May 2011 20:34:08 +0200	[thread overview]
Message-ID: <BANLkTikOsqazAE-mHFrM+=4GTs+249Ae5Q@mail.gmail.com> (raw)
In-Reply-To: <20110519174420.GD12525@obsidianresearch.com>

On Thu, May 19, 2011 at 7:44 PM, Jason Gunthorpe
<jgunthorpe@obsidianresearch.com> wrote:
> On Thu, May 19, 2011 at 07:29:21PM +0200, Bart Van Assche wrote:
> > Regarding APM: the Linux kernel already has multipath support and
> > duplicate functionality is in general not welcomed. So you will have
> > to come up with a very good reason before APM support in ib_srp or
> > ib_srpt would be considered for acceptance.
>
> APM is a feature of IB's tranport layerthat provides disruption free
> lossless failover to a backup network path completely transparently to
> the application (eg SRP in this case).
>
> This plays a similar role in the IB stack to the realtime spanning
> tree protocol that ethernet uses, or the multipath IP routing that is
> already in the net stack. I don't see it duplicating SCSI multipath at
> all. On very large IB networks (eg > 1000 switches) the rate of link
> failures is high enough that taking an application level recovery on
> hundreds of nodes due to a link failure is troublesome.
>
> If ib_srpt is implemented properly it may already support APM because
> APM is supported by the IB CM that it relies on to setup connections,
> and any SRP client could already request APM functionality during
> connection setup.

My reply applies to your original statement where you were referring
to APM with different destination ports. What you write above is about
APM with identical destination ports and hence does not apply to my
reply.

Bart.

  reply	other threads:[~2011-05-19 18:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18  1:36 [RFC] ib_srpt: initial .40-rc1 drivers/infiniband/ulp/srpt merge Nicholas A. Bellinger
2011-05-18  7:47 ` Christoph Hellwig
     [not found]   ` <20110518074716.GA8927-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2011-05-18 16:46     ` Roland Dreier
2011-05-19  6:00     ` Nicholas A. Bellinger
2011-05-18 16:59 ` Bart Van Assche
     [not found]   ` <BANLkTi=e+v7PLcSc8GNov-TOXFF7rurXew-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-18 17:05     ` Jason Gunthorpe
2011-05-18 18:02       ` Bart Van Assche
2011-05-18 19:17         ` Roland Dreier
     [not found]           ` <BANLkTi==bZ0h3o5FNrg8PSJFp6F-zh5hTA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-19  4:18             ` Nicholas A. Bellinger
     [not found]               ` <1305778694.2856.533.camel-Y1+j5t8j3WgjMeEPmliV8E/sVC8ogwMJ@public.gmane.org>
2011-05-19 10:40                 ` Bart Van Assche
2011-05-19 16:57                   ` Jason Gunthorpe
     [not found]                   ` <BANLkTi=Xb-ypQNa3=MmwiLeE4Q9FWHnZXg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-19 20:03                     ` Nicholas A. Bellinger
     [not found]       ` <20110518170556.GB2595-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2011-05-19 17:29         ` Bart Van Assche
     [not found]           ` <BANLkTikOCeNcDvoCM=BOSxQaSECFhJ05Gg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-19 17:44             ` Jason Gunthorpe
2011-05-19 18:34               ` Bart Van Assche [this message]
     [not found]                 ` <BANLkTikOsqazAE-mHFrM+=4GTs+249Ae5Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-19 18:41                   ` Jason Gunthorpe
2011-05-22 19:14                     ` Bart Van Assche

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='BANLkTikOsqazAE-mHFrM+=4GTs+249Ae5Q@mail.gmail.com' \
    --to=bvanassche@acm.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dillowda@ornl.gov \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --cc=roland@purestorage.com \
    --cc=vu@mellanox.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;
as well as URLs for NNTP newsgroup(s).