Closed mcbridematt closed 1 year ago
@mcbridematt Same as https://github.com/mcusim/freebsd-src/issues/8#issuecomment-1655446455
Excellent! I've tested with four ports active (GENERIC-NODEBUG) and it has gone 24 hours without issues.
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-86400.00 sec 7.46 TBytes 760 Mbits/sec 360862 sender
[ 5] 0.00-86400.00 sec 7.46 TBytes 760 Mbits/sec receiver
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-86400.00 sec 6.78 TBytes 690 Mbits/sec 95783 sender
[ 5] 0.00-86400.00 sec 6.78 TBytes 690 Mbits/sec receiver
I'll move my 'production' FreeBSD machine to this version and see how it goes.
I'll move my 'production' FreeBSD machine to this version and see how it goes.
I hope I'll still have a chance to commit those changes till 14.0. Thanks for testing and help!
Commit: 5f6b8b38dfebacb69aad59122e86d18484e7e3c1
In my test suite, I run iperf3 through the FreeBSD host functioning as a router
For example: iperf3 server <-> dpniX (FreeBSD) dpniX+1 <-> iperf3 client
The test system is another Ten64 running Linux which runs each iperf3 instance in a container with one of the ethX ports transferred into it.
So dpni0 on FreeBSD -> eth0 on test system, dpni1<->eth1, dpni2<->eth2 etc.
(I'll publish the scripts another time, they need a bit of cleanup)
dpni6 is the interface to my LAN for management
Server 1 is attached to dpni0 on 192.168.13.2 Client 1 is on dpni2, gets an IP via DHCP and initiates an
iperf3 -R -c 192.168.13.2
Server 2 on 192.168.15.2, Client 2 on 192.168.16.X so on.For this initial test, I will run just one flow.
On this branch, the dataflow completely stops almost immediately:
In this case, dpni1 won't receive any traffic to the iperf3 server (192.168.13.2), but will receive other frames:
vmstat:
I do a few more vmstats:
its0,140: dpaa2_io0
counter has not changed, is it stuck?dpaa2 niX counters: