Date: Wed, 21 Jun 2017 23:24:27 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220198] igb stats double counting in 12-CURRENT Message-ID: <bug-220198-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220198 Bug ID: 220198 Summary: igb stats double counting in 12-CURRENT Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: woodsb02@freebsd.org My networking statistics appear to be double counting on two of my FreeBSD 12-CURRENT boxes running r319025. I discovered the double counting by comparing the output of "systat -ifstat" (which reports 988 KB/s) with the output of "iftop -B" (which reports 491 KB/s). I believe systat uses the kernel interface counters to infer bandwid= th usage, whereas iftop gathers statistics using pcap. I know that iftop is the correct one, because my internet speed only gives me around ~500 KB/s unfortunately. # systat -ifstat -match igb0 ... Interface Traffic Peak Total igb0 in 988.008 KB/s 988.008 KB/s 36.295 GB out 16.953 KB/s 16.953 KB/s 295.774 GB # iftop -i igb0 -B ... TX: cum: 31.7KB peak: 9.69KB rates: 9.69KB 7.92KB 7.92KB RX: 1.54MB 491KB 491KB 394KB 394KB The two interfaces in these boxes are: $ pciconf -lvv | grep igb1 -A4 igb1@pci0:4:0:0: class=3D0x020000 card=3D0x00008086 chip=3D0x1539808= 6 rev=3D0x03 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'I211 Gigabit Network Connection' class =3D network subclass =3D ethernet $ pciconf -lvv | grep igb0 -A4 igb0@pci0:8:0:0: class=3D0x020000 card=3D0x15331849 chip=3D0x1533808= 6 rev=3D0x03 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'I210 Gigabit Network Connection' class =3D network subclass =3D ethernet --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220198-8>