On Tue, Nov 01, 2011 at 11:46:08PM +0200, Or Gerlitz wrote: > > In the same vien adding saturating but non-resettable PMA-esque > > counters for IBoE seems pretty hackish to me.. Though I agree it is > > not terribly relevant for 64 bit counters. > To put things in place, the IB stack PMA counters aren't resettable > through sysfs, still, under IB, the same counter set is readable > through both mads and sysfs and resettable through mads.
Right, the sysfs interface is pretty much unusable for IB. Your work to make it go on IBoE makes something is very nearly usuable, but you can't write a tool that collects these counters from a port in IBoE mode and also expect it to work in IB mode because the semantics are different. My argument here is that the semantics we have for the IB case are not useful. Let us define sane semantics for the IBoE case and have a longer term clean up to make the IB case follow them as well. Sane semantics for a sysfs counter are: - Free-running - Non-saturating - No reset - 64 or 32 bit value, detectable by user-space No 6 bit counters. No counters that saturate. No counters that randomly reset. To this end, I think exporting 64 bit and 32 bit counts of the same value is not the way to go. > As for the saturation thing, I didn't think about that, but you're > probably right and all the IBA PMA counters are saturating, but as > your comment said, the 64 bit case is practically okay Will any counters that get exposed when IBoE is turned on not be 64 bits? There are not very many 64 bit PMA counters. If yes, maybe you should patch to un-export them until things can be fixed sanely... Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
