[Bug 280386] if_bridge throws output errors under load

From: <bugzilla-noreply_at_freebsd.org>
Date: Fri, 09 Aug 2024 03:12:53 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280386

--- Comment #18 from pascal.guitierrez@gmail.com ---
(In reply to Aleksandr Fedorov from comment #17)

currently at default of dev.igb.0.fc=3

changing it has no apparent effect.

however what i notice is that re-running the test results in some tests having
0 errors occur and others consistent errors, see below output from iperf3 with
only 2 parallel tests (system has 4 cores):

this test had no errors (see the "Retr" field):

iperf3 -P2 -c 192.168.0.5 -t 600
Connecting to host 192.168.0.5, port 5201
[  5] local 192.168.0.150 port 47836 connected to 192.168.0.5 port 5201
[  7] local 192.168.0.150 port 12391 connected to 192.168.0.5 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  57.8 MBytes   484 Mbits/sec    0   2.00 MBytes       
[  7]   0.00-1.00   sec  57.9 MBytes   485 Mbits/sec    0   2.00 MBytes       
[SUM]   0.00-1.00   sec   116 MBytes   969 Mbits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   1.00-2.00   sec  56.1 MBytes   471 Mbits/sec    0   2.00 MBytes       
[  7]   1.00-2.00   sec  56.0 MBytes   470 Mbits/sec    0   2.00 MBytes       
[SUM]   1.00-2.00   sec   112 MBytes   941 Mbits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   2.00-3.00   sec  56.1 MBytes   471 Mbits/sec    0   2.00 MBytes       
[  7]   2.00-3.00   sec  56.2 MBytes   472 Mbits/sec    0   2.00 MBytes       
[SUM]   2.00-3.00   sec   112 MBytes   943 Mbits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   3.00-4.00   sec  56.0 MBytes   470 Mbits/sec    0   2.00 MBytes       
[  7]   3.00-4.00   sec  56.0 MBytes   470 Mbits/sec    0   2.00 MBytes       
[SUM]   3.00-4.00   sec   112 MBytes   940 Mbits/sec    0             
^C- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   4.00-4.55   sec  30.6 MBytes   469 Mbits/sec    0   2.00 MBytes       
[  7]   4.00-4.55   sec  30.8 MBytes   471 Mbits/sec    0   2.00 MBytes       
[SUM]   4.00-4.55   sec  61.4 MBytes   941 Mbits/sec    0             


then if run again, it may experience errors, and if it does, the errors are
consistently seen for the rest of the test run:

iperf3 -P2 -c 192.168.0.5 -t 600
Connecting to host 192.168.0.5, port 5201
[  5] local 192.168.0.150 port 60974 connected to 192.168.0.5 port 5201
[  7] local 192.168.0.150 port 30555 connected to 192.168.0.5 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  48.5 MBytes   406 Mbits/sec    6   2.00 MBytes       
[  7]   0.00-1.00   sec  67.0 MBytes   560 Mbits/sec    3   2.00 MBytes       
[SUM]   0.00-1.00   sec   116 MBytes   966 Mbits/sec    9             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   1.00-2.00   sec  52.5 MBytes   441 Mbits/sec   12   1.41 MBytes       
[  7]   1.00-2.00   sec  59.5 MBytes   500 Mbits/sec    4   1.44 MBytes       
[SUM]   1.00-2.00   sec   112 MBytes   941 Mbits/sec   16             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   2.00-3.00   sec  58.5 MBytes   490 Mbits/sec    2   1011 KBytes       
[  7]   2.00-3.00   sec  54.2 MBytes   454 Mbits/sec    3    510 KBytes       
[SUM]   2.00-3.00   sec   113 MBytes   944 Mbits/sec    5             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   3.00-4.00   sec  53.0 MBytes   445 Mbits/sec    3   2.00 MBytes       
[  7]   3.00-4.00   sec  59.2 MBytes   497 Mbits/sec    3    168 KBytes       
[SUM]   3.00-4.00   sec   112 MBytes   942 Mbits/sec    6             
^C- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   4.00-4.64   sec  42.5 MBytes   559 Mbits/sec    2    338 KBytes       
[  7]   4.00-4.64   sec  29.0 MBytes   381 Mbits/sec    1   2.00 MBytes       
[SUM]   4.00-4.64   sec  71.5 MBytes   941 Mbits/sec    3             

the behaviour occurs independently of the dev.igb.0.fc value (3 or 0)

-- 
You are receiving this mail because:
You are the assignee for the bug.