From: "ira.weiny" <ira.weiny@intel.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Michael Wang <yun.wang@profitbricks.com>,
Nicholas Krause <xerofoify@gmail.com>,
dledford@redhat.com, sean.hefty@intel.com,
hal.rosenstock@gmail.com, haggaie@mellanox.com,
matanb@mellanox.com, doront@mellanox.com, david.ahern@oracle.com,
erezsh@mellanox.com, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] infiniband:core:Add needed error path in cm_init_av_by_path
Date: Wed, 16 Dec 2015 01:52:22 -0500 [thread overview]
Message-ID: <20151216065222.GA27524@phlsvsds.ph.intel.com> (raw)
In-Reply-To: <20151215173022.GB25965@obsidianresearch.com>
On Tue, Dec 15, 2015 at 10:30:22AM -0700, Jason Gunthorpe wrote:
> On Tue, Dec 15, 2015 at 05:38:34PM +0100, Michael Wang wrote:
> > The hop_limit is only suggest that the package allowed to be
> > routed, not have to, correct?
>
> If the hop limit is >= 2 (?) then the GRH is mandatory.
Yes >= 2.
"Setting this value to 0 or 1 will ensure that the packet
will not be forwarded beyond the local subnet."
-- IBTA 8.3.6 Hop Limit
Ira
> The
> SM will return this information in the PathRecord if it determines a
> GRH is required. The whole stack follows this protocol.
>
> The GRH is optional for in-subnet communications.
>
> Jason
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-12-16 6:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1450194724-7107-1-git-send-email-xerofoify@gmail.com>
2015-12-15 16:38 ` [PATCH RESEND] infiniband:core:Add needed error path in cm_init_av_by_path Michael Wang
2015-12-15 17:30 ` Jason Gunthorpe
2015-12-16 6:52 ` ira.weiny [this message]
2015-12-16 10:26 ` Michael Wang
2015-12-16 18:16 ` Jason Gunthorpe
2015-12-17 8:43 ` Michael Wang
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=20151216065222.GA27524@phlsvsds.ph.intel.com \
--to=ira.weiny@intel.com \
--cc=david.ahern@oracle.com \
--cc=dledford@redhat.com \
--cc=doront@mellanox.com \
--cc=erezsh@mellanox.com \
--cc=haggaie@mellanox.com \
--cc=hal.rosenstock@gmail.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matanb@mellanox.com \
--cc=sean.hefty@intel.com \
--cc=xerofoify@gmail.com \
--cc=yun.wang@profitbricks.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