From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: pierre orzechowski
<pierre.e.orzechowski-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: ibswitches command displays wrong information when switch description string includes "base"
Date: Fri, 6 Jan 2012 17:51:44 -0700 [thread overview]
Message-ID: <20120107005144.GB329@obsidianresearch.com> (raw)
In-Reply-To: <4F079048.8050709-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
On Fri, Jan 06, 2012 at 04:22:32PM -0800, pierre orzechowski wrote:
> We have a customer reporting an issue with the "ibswitches" command
> part of the infiniband-diags package.
> If the switch description includes the string "base" anywhere, then
> the match operation in the awk section of ibwitches does not behave
> as expected and output is garbled.
These shell tools have all been de-supported by the infiniband-diags
maintainer, exactly because they are prone to these sorts of problems
due to inherent design flaws.
The recommendation is to use the new C based commands, but there is
not an exact correspondence.
python-rdma's ibtool command has work-alikes for all of the old
commands that do not have these issues for people who absolutely must
have the old commands.
Jason
--
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
next prev parent reply other threads:[~2012-01-07 0:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 0:22 ibswitches command displays wrong information when switch description string includes "base" pierre orzechowski
[not found] ` <4F079048.8050709-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2012-01-07 0:51 ` Jason Gunthorpe [this message]
2012-01-12 7:36 ` Ira Weiny
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=20120107005144.GB329@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pierre.e.orzechowski-QHcLZuEGTsvQT0dZR+AlfA@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