[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110519184113.GE12525@obsidianresearch.com>
Date: Thu, 19 May 2011 12:41:13 -0600
From: Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To: Bart Van Assche <bvanassche@....org>
Cc: "Nicholas A. Bellinger" <nab@...ux-iscsi.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-scsi <linux-scsi@...r.kernel.org>,
linux-rmda <linux-rdma@...r.kernel.org>,
Roland Dreier <roland@...estorage.com>,
Vu Pham <vu@...lanox.com>, David Dillow <dillowda@...l.gov>,
James Bottomley <James.Bottomley@...senpartnership.com>
Subject: Re: [RFC] ib_srpt: initial .40-rc1 drivers/infiniband/ulp/srpt
merge
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists