On Thu, 10 Jun 2010 09:04:01 -0700
"Hefty, Sean" <[email protected]> wrote:
> Sasha,
>
> Before we do the work, would there be any issue converting a couple of the
> ib-diag scripts to executables? Specifically, we'd like to have ibchecknet
> and ibcheckerrors functionality available on Windows.
>
Here at LLNL we were thinking it would be best to start removing some of the
scripts to reduce the confusion about what tools do. For example, there is
some confusion among our users as to what ibcheckerrs, ibcheckerrors, and
ibqueryerrors does?
AFAICT ibcheckerrors and ibqueryerrors only differ in 3 respects.
1) the formated output is different
2) ibcheckerrors calls ibcheckerrs which ignores error counts which are
below a threshold either hard coded or specified by a file.
3) ibcheckerrs defaults to use AllPortSelect which may result in a faster
scan. [*]
[*] I have a patch for ibqueryerrors which querys AllPortSelect first
and only issues individual queries if it sees errors. However, frankly
it did not seem to speed up the scan on our large clusters so I don't
know if this is a big difference between ibcheckerrors and
ibqueryerrors.)
2 is very easy to add to ibqueryerrors, I don't think 1 would be that hard,
and 3 is basically done.
As for ibchecknet, under what use case do you see people running it? Could
ibnetdiscover or iblinkinfo provide the same functionality?
Ira
> - Sean
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to [email protected]
> More majordomo info at http://*vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
