public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cook <acook-osxm6dDZNBBZx8iatJs59jGjJy/sRE9J@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Unable to Connect Using Active Speed 2.5 Gbps and Active Width of 1
Date: Tue, 29 Mar 2011 18:01:13 +0000 (UTC)	[thread overview]
Message-ID: <loom.20110329T195143-723@post.gmane.org> (raw)
In-Reply-To: 4D9218F0.3020000@dev.mellanox.co.il

Hal Rosenstock <hal@...> writes:
> 
> How about if rather than Test, you change it to Default=0x7fff ?
> 

I tried using the PKey since posting, but it alone did not solve the issue.

> 
> The above is pertinent to IPoIB ping but couldn't explain ibping lack of 
> connectivity.
> 

Turns out I was using the wrong port GUID (bad copy and paste) when testing with
ibping. It has been working all along.

I have just now solved the issue.

The partitions.conf file took me in the right direction.  The solution was to
use rate=2 instead of as rate=1 (which apparently is a reserved value).  I was
unable find documentation for the rate-value pairs, so I was assuming that
rate=1 was 2.5.  I finally found documentation for the rates in a post on the
old ofa-general mailing list:

#define IB_PATH_RECORD_RATE_2_5_GBS             2
#define IB_PATH_RECORD_RATE_10_GBS              3
#define IB_PATH_RECORD_RATE_30_GBS              4
#define IB_PATH_RECORD_RATE_5_GBS               5
#define IB_PATH_RECORD_RATE_20_GBS              6
#define IB_PATH_RECORD_RATE_40_GBS              7
#define IB_PATH_RECORD_RATE_60_GBS              8
#define IB_PATH_RECORD_RATE_80_GBS              9
#define IB_PATH_RECORD_RATE_120_GBS             10

#define IB_MIN_RATE    IB_PATH_RECORD_RATE_2_5_GBS
#define IB_MAX_RATE    IB_PATH_RECORD_RATE_120_GBS

Setting my partitions.conf as follows has solved the issue:

Default=0x7fff,ipoib,rate=2:ALL=full;

Thanks everyone for the help.

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

  reply	other threads:[~2011-03-29 18:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28 18:01 Unable to Connect Using Active Speed 2.5 Gbps and Active Width of 1 Alan Cook
     [not found] ` <loom.20110328T194956-774-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-03-28 18:55   ` Hal Rosenstock
2011-03-28 19:07     ` Alan Cook
     [not found]       ` <loom.20110328T210350-244-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-03-28 19:19         ` Hal Rosenstock
2011-03-28 19:26           ` Alan Cook
     [not found]             ` <loom.20110328T212117-950-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-03-28 19:41               ` Jason Gunthorpe
2011-03-28 20:41                 ` Alan Cook
     [not found]                   ` <loom.20110328T220853-101-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-03-29 17:37                     ` Hal Rosenstock
2011-03-29 18:01                       ` Alan Cook [this message]
2011-03-28 20:18               ` 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=loom.20110329T195143-723@post.gmane.org \
    --to=acook-osxm6ddznbbzx8iatjs59jgjjy/sre9j@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