Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Sep 2016 22:28:53 +0200
From:      Ben RUBSON <ben.rubson@gmail.com>
To:        FreeBSD Net <freebsd-net@freebsd.org>
Subject:   Re: netstat counts input traffic twice
Message-ID:  <D24FF41D-F459-4FCE-8378-1C843DDC4CF8@gmail.com>
In-Reply-To: <4f5a88f4-03e7-482f-b963-ab65eeee0136@selasky.org>
References:  <94953762-4397-476D-AD61-A39914F27938@gmail.com> <6d052c64-2ca2-7839-c297-e764634be648@selasky.org> <AED1E1B1-424E-4932-A7F5-80410505E15C@gmail.com> <4f5a88f4-03e7-482f-b963-ab65eeee0136@selasky.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 28 Sep 2016, at 18:00, Hans Petter Selasky <hps@selasky.org> wrote:
>=20
> On 09/28/16 17:48, Ben RUBSON wrote:
>>=20
>>> On 28 Sep 2016, at 16:01, Hans Petter Selasky <hps@selasky.org> =
wrote:
>>>=20
>>> On 09/23/16 19:59, Ben RUBSON wrote:
>>>> netstat -b -I mlxen1
>>>=20
>>> Hi Ben,
>>>=20
>>> Does the attached patch make any difference?
>>=20
>> Hi HPS,
>>=20
>> I tested your patch, but unfortunately it does not help.
>=20
> Is this a regression issue from 10.x ?

I booted a 10.3 ISO and made the test, 10.3 does not suffer from the =
issue :

Here is iperf on sending side :

[  3]  0.0- 1.0 sec   231 MBytes  1.93 Gbits/sec
[  3]  1.0- 2.0 sec   660 MBytes  5.53 Gbits/sec
[  3]  2.0- 3.0 sec   686 MBytes  5.75 Gbits/sec
[  3]  3.0- 4.0 sec   685 MBytes  5.75 Gbits/sec
[  3]  4.0- 5.0 sec   688 MBytes  5.77 Gbits/sec
[  3]  5.0- 6.0 sec   688 MBytes  5.77 Gbits/sec
[  3]  6.0- 7.0 sec   687 MBytes  5.76 Gbits/sec
[  3]  7.0- 8.0 sec   686 MBytes  5.75 Gbits/sec
[  3]  8.0- 9.0 sec   688 MBytes  5.77 Gbits/sec
[  3]  9.0-10.0 sec   688 MBytes  5.77 Gbits/sec
[  3]  0.0-10.0 sec  6.24 GBytes  5.36 Gbits/sec

And here is netstat on receiving side :

# netstat -w 1 -i mlxen1
            input        (Total)           output
   packets  errs idrops      bytes    packets  errs      bytes colls
         3     0     0    1342564          2     0        242     0
     20010     0     0  288125410       9861     0     690494     0
     76138     0     0  714913534      37134     0    2599418     0
     84279     0     0  720127612      40735     0    2851628     0
     84629     0     0  725851168      40776     0    2854428     0
     84132     0     0  736770514      40658     0    2846168     0
     83584     0     0  717375282      40657     0    2846092     0
     83669     0     0  734551794      40825     0    2857858     0
     83854     0     0  716303392      40866     0    2860748     0
     83944     0     0  730653274      40795     0    2855752     0
     84523     0     0  663718362      41136     0    2879616     0
      9844     0     0     190720       4769     0     334016     0

Receiving side info :

# uname -a
FreeBSD test 10.3-RELEASE FreeBSD 10.3-RELEASE #0 r297264: Fri Mar 25 =
02:10:02 UTC 2016
root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
# grep -i "mlx.*driver" /var/log/messages
kernel: mlx4_core: Initializing mlx4_core: Mellanox ConnectX VPI driver =
v2.1.6 (Apr 9 2016)

> Does other network drivers exhibit the same behaviour?

I only run FreeBSD with ConnectX3 NICs, so I can't test other hardware =
:-/

> With your instructions I should be able to reproduce and fix this =
issue.

Thank you, and of course feel free to ask again if needed.

Ben




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D24FF41D-F459-4FCE-8378-1C843DDC4CF8>