From: Devesh Sharma <devesh.sharma@broadcom.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: linux-rdma <linux-rdma@vger.kernel.org>,
Jason Gunthorpe <jgg@mellanox.com>
Subject: Re: [PATCH v8] libibverbs: display gid type in ibv_devinfo
Date: Thu, 13 Feb 2020 00:22:40 +0530 [thread overview]
Message-ID: <CANjDDBi6S04wAwzsum_utZCsf2YxaX1qiffaT4iUD-56hjBzEA@mail.gmail.com> (raw)
In-Reply-To: <20200212175458.GE679970@unreal>
On Wed, Feb 12, 2020 at 11:25 PM Leon Romanovsky <leon@kernel.org> wrote:
>
> On Mon, Feb 10, 2020 at 12:17:45PM -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:0000:0000:0000:b226:28ff:fed3:b0f0, RoCE v1
> > GID[ 1]: fe80::b226:28ff:fed3:b0f0, RoCE v2
> > GID[ 2]: 0000:0000:0000:0000:0000:ffff:c0aa:0165, RoCE v1
> > GID[ 3]: ::ffff:192.170.1.101, RoCE v2
> > $
> > $
> > $
> >
> > Reviewed-by: Jason Gunthrope <jgg@ziepe.ca>
> > Reviewed-by: Gal Pressman <galpress@amazon.com>
> > Reviewed-by: Parav Pandit <parav@mellanox.com>
> > Signed-off-by: Devesh Sharma <devesh.sharma@broadcom.com>
> > ---
> > libibverbs/examples/devinfo.c | 61 ++++++++++++++++++++++++++++++++++---------
> > 1 file changed, 49 insertions(+), 12 deletions(-)
> >
>
> Devesh,
>
> I see that everyone is happy now, can you please refresh PR so I will
> merge it?
>
> Thanks,
> Reviewed-by: Leon Romanovsky <leonro@mellanox.com>
Done
Thanks!
prev parent reply other threads:[~2020-02-12 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 17:17 [PATCH v8] libibverbs: display gid type in ibv_devinfo Devesh Sharma
2020-02-12 17:54 ` Leon Romanovsky
2020-02-12 18:52 ` Devesh Sharma [this message]
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=CANjDDBi6S04wAwzsum_utZCsf2YxaX1qiffaT4iUD-56hjBzEA@mail.gmail.com \
--to=devesh.sharma@broadcom.com \
--cc=jgg@mellanox.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;
as well as URLs for NNTP newsgroup(s).