From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: "Hefty,
Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: REQ GID enforcement in the CM
Date: Mon, 31 Oct 2011 12:19:45 -0600 [thread overview]
Message-ID: <20111031181945.GY26974@obsidianresearch.com> (raw)
In-Reply-To: <4EAD239A.2050702-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
On Sun, Oct 30, 2011 at 12:14:50PM +0200, Or Gerlitz wrote:
> On 10/27/2011 6:55 PM, Jason Gunthorpe wrote:
> >You can use the CM to establish a connection on another port, eg
> >send CM GMPs to port 1, specify the primary data path is port 2
> >and specify the alternate data path is port 1. Jason
>
> makes sense, still, maybe the code here could/should be made more
> strict here for the case of a REQ sent with primary path only,
> agree?
I'm not quite sure what you are proposing?
IBA places no requirements on the how the GMP path for CM messages is
related to the data path.
The only validation you can do is to ensure that end port described by
the GID also has the LID as part of its LID/LMC range, which I thought
I saw happening?
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-10-31 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 14:14 REQ GID enforcement in the CM Or Gerlitz
[not found] ` <4EA9672F.2010601-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2011-10-27 16:55 ` Jason Gunthorpe
[not found] ` <20111027165522.GA16878-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2011-10-30 10:14 ` Or Gerlitz
[not found] ` <4EAD239A.2050702-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2011-10-31 18:19 ` Jason Gunthorpe [this message]
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=20111031181945.GY26974@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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