From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Bart Van Assche <bvanassche@acm.org>
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 12:41:13 -0600 [thread overview]
Message-ID: <20110519184113.GE12525@obsidianresearch.com> (raw)
In-Reply-To: <BANLkTikOsqazAE-mHFrM+=4GTs+249Ae5Q@mail.gmail.com>
On Thu, May 19, 2011 at 08:34:08PM +0200, Bart Van Assche wrote:
> 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.
The subnet manager can give an APM result that will switch between
ports on the same node, APM handles both switching to a different path
with the same end ports, and also switching to a new path using the
same end ports. An implementation supporting APM must be ready for
both situations - realistically no additional app code is required to
support the multiport case since it falls out for free. You'd actually
have to actively work to prevent it...
This is why in the IB verbs architecture nearly everything is tied to
a *device*, not a port.
Jason
next prev parent reply other threads:[~2011-05-19 18:41 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
2011-05-18 16:46 ` Roland Dreier
2011-05-19 6:00 ` Nicholas A. Bellinger
2011-05-18 16:59 ` Bart Van Assche
2011-05-18 17:05 ` Jason Gunthorpe
2011-05-18 18:02 ` Bart Van Assche
2011-05-18 19:17 ` Roland Dreier
2011-05-19 4:18 ` Nicholas A. Bellinger
2011-05-19 10:40 ` Bart Van Assche
2011-05-19 16:57 ` Jason Gunthorpe
2011-05-19 20:03 ` Nicholas A. Bellinger
2011-05-19 17:29 ` Bart Van Assche
2011-05-19 17:44 ` Jason Gunthorpe
2011-05-19 18:34 ` Bart Van Assche
2011-05-19 18:41 ` Jason Gunthorpe [this message]
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=20110519184113.GE12525@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bvanassche@acm.org \
--cc=dillowda@ornl.gov \
--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).