From: Leon Romanovsky <leon@kernel.org>
To: Benjamin Drung <benjamin.drung@ionos.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: iblinkinfo for Python
Date: Thu, 6 Jan 2022 16:39:48 +0200 [thread overview]
Message-ID: <Ydb/NGTqH/IRXF16@unreal> (raw)
In-Reply-To: <6a517f87daa4c6d4fe93327fb0645d1698bc7556.camel@ionos.com>
On Wed, Jan 05, 2022 at 01:05:08PM +0100, Benjamin Drung wrote:
> Am Mittwoch, dem 05.01.2022 um 13:52 +0200 schrieb Leon Romanovsky:
> > On Wed, Jan 05, 2022 at 11:32:40AM +0100, Benjamin Drung wrote:
> > > Hi,
> > >
> > > we have an in-house Shell script that uses iblinkinfo to check if the
> > > InfiniBand cabling is correct. This information can be derived from
> > > the
> > > node names that can be seen for the HCA port. I want to improve that
> > > check and rewrite it in Python, but I failed to find an easy and
> > > robust
> > > way to retrieve the node names for a HCA port:
<...>
> > > What should I do?
<...>
The iblinkinfo receives this information through umad interface, so if I
would be you, I would write the simplified version of iblinkinfo.
Thanks
next prev parent reply other threads:[~2022-01-06 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 10:32 iblinkinfo for Python Benjamin Drung
2022-01-05 11:52 ` Leon Romanovsky
2022-01-05 12:05 ` Benjamin Drung
2022-01-06 14:39 ` Leon Romanovsky [this message]
2022-01-11 12:28 ` Jens Domke
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=Ydb/NGTqH/IRXF16@unreal \
--to=leon@kernel.org \
--cc=benjamin.drung@ionos.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.