[ofw] ib-diags: compatability issue with ibstat

[Hefty, Sean]

> > The only way to determine whether fdr10 is active or not is via the
> > vendor proprietary MAD. That info may be reflected in some other API
> > (and/or file) so that MAD does not need to be reissued. In a separate
> > thread on linux-rdma, there was discussion on a couple of different
> > ways to do that from verbs and in this thread that there's no sysfs
> > equivalent in Windows. You've already stated that the Windows support
> > is using libibverbs for libibumad support so it seems appropriate to
> > me to do the same here (in Windows at least).
> 
> The proper place for is_fdr10 is in libibumad (and then we wouldn't be
> discussing libibverbs w/ibstat) but that was not done to avoid a
> change to the umad port structure.

ibstat determines is_fdr10 by reading a file.  That same data could just as easily be exported as a port attribute, which would make it belong to ibverbs, rather than umad.

If the only point of exporting is_fdr10 from the kernel is for an ib management diag to display the value, then it's not a useful value for verbs applications.