Date: Sat, 4 Aug 2012 18:29:20 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Ian Lepore <freebsd@damnhippie.dyndns.org> Cc: freebsd-hackers <freebsd-hackers@freebsd.org> Subject: Re: How to Expose Chip-level Ethernet Statistics? Message-ID: <B4511C5B-FB33-4AC7-A0DC-1DE740ACE1EE@freebsd.org> In-Reply-To: <1344109912.1128.94.camel@revolution.hippie.lan> References: <D964DD93-51C6-43AE-B18A-09DEC4AB59FA@freebsd.org> <1344109912.1128.94.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 4, 2012, at 12:51 PM, Ian Lepore wrote: > On Sat, 2012-08-04 at 12:21 -0700, Tim Kientzle wrote: >> I believe that some of the issues I'm having with this >> Ethernet driver might be easier to diagnose if I could >> expose the chip-level statistics counters (especially queue >> overrun counts). >>=20 >> Is there a standard way to do this? >>=20 >=20 > I don't know if this is exactly what you mean, but have a look at > src/tools/tools/ifinfo, and find some examples of drivers that fill in > that info by grepping for ifmib_iso_8802_3. >=20 > (I really know nothing about this stuff, except that your request > triggered a memory that the atmel if_ate driver gathers some stats = that > I've not seen in most other drivers.) Thanks, Ian! That's almost exactly what I'm looking for. Only tricky point: I don't immediately see where the standard MIB allows me to run a function when the sysctl query runs (which will be necessary if I want to expose the on-chip counters). That might lead me to use a separate sysctl tree for this. I'll also take at the atmel if_ate driver=85. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B4511C5B-FB33-4AC7-A0DC-1DE740ACE1EE>