From: Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org>
To: Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Cc: Hal Rosenstock
<hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Hal Rosenstock
<hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 2/3] infiniband-diags: libibnetdisc Allow a DR Path partial fabric query starting at a CA
Date: Fri, 22 Jul 2011 15:00:49 -0700 [thread overview]
Message-ID: <20110722150049.ba8e592f.weiny2@llnl.gov> (raw)
In-Reply-To: <20110722172945.GP18090-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
On Fri, 22 Jul 2011 10:29:46 -0700
Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org> wrote:
> On Fri, Jul 22, 2011 at 09:21:13AM -0400, Hal Rosenstock wrote:
> > On 7/20/2011 7:34 PM, Jason Gunthorpe wrote:
> > > Also, there is a bug, you can't DLID route to the local HCA and then
> > > use that as a source of a DR path, even though intuitively that should
> > > work.
> >
> > Just the local xCA or any xCA ?
>
> Well both, but I was under the impression that latter was specified
> behavior, but I haven't looked it up.
I agree it would be nice if one could issue a combined path and "scan through"
any xCA on the fabric. However, I don't think it is allowed, nor correct to
do so.
The informative text on pg 805 ln 23 specifically states that the initial LID
routing is from "source node to source switch".
Furthermore, C14-7 (continued on pg 809, first bullet) specifically indicates
that the DLID for an initial LID routed DR SMP "shall be set to the LID of the
source switch in the DR part."
^^^^^^
Even if this is considered vague there would be a problem a xCA was allowed.
C14-9 "case 1" would allow an SM to "scan through" a xCA to another subnet.
Or actually it would result in the SMP being "lost" in the other subnet.
For example take the following:
"Local subnet" "Other subnet"
xCA1 ----> switch ----> xCA2 p1 : xCA2 p2 ----> switch -> ...
LIDs 2 3 4 1 2
If I issue the SMP from xCA1 with DrSLID = 3 and a DR path of 0,2. xCA2 will
alter the fields as per C14-9 and issue the SMP out port 2.
Then, when the response comes back to xCA2 p2, it will attempt to
send the packet to LID 2 (DrSLID == 2 from the original query) and the SMP
will end up at the switch on the right in "other subnet", _not_ at xCA1
So although I don't see a specific compliance (and I agree it would be nice) I
think it is safe to say that it should be restricted.
Would it be more clear for C14-9 to specifically exclude this case?
Ira
>
> Jason
--
Ira Weiny
Math Programmer/Computer Scientist
Lawrence Livermore National Lab
925-423-8008
weiny2-i2BcT+NCU+M@public.gmane.org
--
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
next prev parent reply other threads:[~2011-07-22 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 23:16 [PATCH 2/3] infiniband-diags: libibnetdisc Allow a DR Path partial fabric query starting at a CA Ira Weiny
[not found] ` <20110720161655.1ed38052.weiny2-i2BcT+NCU+M@public.gmane.org>
2011-07-20 23:34 ` Jason Gunthorpe
[not found] ` <20110720233451.GL18090-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2011-07-20 23:53 ` Ira Weiny
[not found] ` <20110720165336.894b1298.weiny2-i2BcT+NCU+M@public.gmane.org>
2011-07-21 3:17 ` Jason Gunthorpe
2011-07-22 13:21 ` Hal Rosenstock
[not found] ` <4E297949.2000607-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2011-07-22 17:29 ` Jason Gunthorpe
[not found] ` <20110722172945.GP18090-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2011-07-22 22:00 ` Ira Weiny [this message]
[not found] ` <20110722150049.ba8e592f.weiny2-i2BcT+NCU+M@public.gmane.org>
2011-07-22 22:13 ` Jason Gunthorpe
[not found] ` <20110722221349.GT18090-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2011-07-22 22:26 ` Ira Weiny
2011-07-22 22:02 ` Hal Rosenstock
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=20110722150049.ba8e592f.weiny2@llnl.gov \
--to=weiny2-i2bct+ncu+m@public.gmane.org \
--cc=hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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