On Mon, Nov 07, 2011 at 04:54:42PM -0800, Roland Dreier wrote: > On Wed, Nov 2, 2011 at 10:16 AM, Or Gerlitz <ogerl...@mellanox.com> wrote: > > I suggest we go that least bad way along the lines of your comment. > > > > If/when on some future point something constructive can be formed from > > Jason's observations, changes will follow, agree? > > Let's make sure we learn from our mistakes. Let's say we create a > new "ext_counters" directory. What should the format of those files > be? Should they be assumed to be 64-bit quantities? Do we want to > allow some way of indicating the number of bits (ie 0-padded hex > entries?)?
That is a good idea. Let's require counters_ext to be sane: 1 Hex quantity of unspecified size 2 Prefixed with 0x and leading zeros to fill out to size and allow userspace discovery of size 3 Size must be a multiple of 4 bits. 4 Counters do not saturate 5 Counters wrap around at all F's back to 0. 6 If the counter is resettable it is only via a local operation through netlink or sysfs or something. Not PMA reset. Certainly, aside from some minor details and different string formatting, the 64 bit counters Or proposes to add meet these requirements when the port is used in Ethernet mode. How do you feel about having counters_ext appear in ethernet mode and disappear in IB mode? 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
