From: Jason Gunthorpe <jgg@mellanox.com>
To: Devesh Sharma <devesh.sharma@broadcom.com>
Cc: linux-rdma@vger.kernel.org, leon@kernel.org
Subject: Re: [PATCH v5] libibverbs: display gid type in ibv_devinfo
Date: Mon, 3 Feb 2020 13:53:17 -0400 [thread overview]
Message-ID: <20200203175317.GQ23346@mellanox.com> (raw)
In-Reply-To: <1580752324-24742-1-git-send-email-devesh.sharma@broadcom.com>
On Mon, Feb 03, 2020 at 12:52:04PM -0500, Devesh Sharma wrote:
> It becomes difficult to make out from the output of ibv_devinfo
> if a particular gid index is RoCE v2 or not.
>
> Adding a string to the output of ibv_devinfo -v to display the
> gid type at the end of gid.
>
> The output would look something like below:
> $ ibv_devinfo -v -d bnxt_re2
> hca_id: bnxt_re2
> transport: InfiniBand (0)
> fw_ver: 216.0.220.0
> node_guid: b226:28ff:fed3:b0f0
> sys_image_guid: b226:28ff:fed3:b0f0
> .
> .
> .
> .
> phys_state: LINK_UP (5)
> GID[ 0]: fe80::b226:28ff:fed3:b0f0, IB/RoCE v1
> GID[ 1]: fe80::b226:28ff:fed3:b0f0, RoCE v2
> GID[ 2]: ::ffff:192.170.1.101, IB/RoCE v1
> GID[ 3]: ::ffff:192.170.1.101, RoCE v2
v1 GIDs are GIDs and should never be formed as IPv6 addreses..
Jason
next prev parent reply other threads:[~2020-02-03 17:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 17:52 [PATCH v5] libibverbs: display gid type in ibv_devinfo Devesh Sharma
2020-02-03 17:53 ` Jason Gunthorpe [this message]
2020-02-03 18:01 ` Devesh Sharma
2020-02-03 18:04 ` Jason Gunthorpe
2020-02-03 18:09 ` Devesh Sharma
2020-02-04 4:27 ` Parav Pandit
2020-02-04 5:08 ` Devesh Sharma
2020-02-04 7:17 ` Leon Romanovsky
2020-02-04 7:25 ` Parav Pandit
2020-02-04 8:44 ` Devesh Sharma
2020-02-04 8:50 ` Devesh Sharma
2020-02-03 19:46 ` Leon Romanovsky
2020-02-04 5:07 ` Devesh Sharma
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=20200203175317.GQ23346@mellanox.com \
--to=jgg@mellanox.com \
--cc=devesh.sharma@broadcom.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.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