public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Ira Weiny <weiny2-i2BcT+NCU+M@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 16:13:49 -0600	[thread overview]
Message-ID: <20110722221349.GT18090@obsidianresearch.com> (raw)
In-Reply-To: <20110722150049.ba8e592f.weiny2-i2BcT+NCU+M@public.gmane.org>

On Fri, Jul 22, 2011 at 03:00:49PM -0700, Ira Weiny wrote:

> 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.

Well, it is explicitly not allowed:

2) If Hop Count is non zero and Hop Pointer is in the range 1  Hop        
   Pointer < Hop Count, this SMI is an intermediate hop in the directed   
   route portion of the path. If the node is not a switch, the SMI shall  
   discard the SMP, otherwise the SMI shall alter the contents of the
   directed route SMP as follows:

> Even if this is considered vague there would be a problem a xCA was allowed.

That sort of behavior is explicitly disallowed in other cases, like
reading port info.

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

  parent reply	other threads:[~2011-07-22 22:13 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
     [not found]                 ` <20110722150049.ba8e592f.weiny2-i2BcT+NCU+M@public.gmane.org>
2011-07-22 22:13                   ` Jason Gunthorpe [this message]
     [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=20110722221349.GT18090@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
    --cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=weiny2-i2BcT+NCU+M@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