| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 24 Feb 2023 19:07:23 +0100
From: Frank Wunderlich <frank-w@...lic-files.de>
To: Arınç ÜNAL <arinc.unal@...nc9.com>
Cc: Vladimir Oltean <olteanv@...il.com>,
netdev <netdev@...r.kernel.org>, erkin.bozoglu@...ont.com,
Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
Felix Fietkau <nbd@....name>, John Crispin <john@...ozen.org>,
Mark Lee <Mark-MC.Lee@...iatek.com>,
Lorenzo Bianconi <lorenzo@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Landen Chao <Landen.Chao@...iatek.com>,
Sean Wang <sean.wang@...iatek.com>,
DENG Qingfang <dqfext@...il.com>
Subject: Aw: Re: Choose a default DSA CPU port
Hi
> Gesendet: Mittwoch, 22. Februar 2023 um 20:42 Uhr
> Von: "Arınç ÜNAL" <arinc.unal@...nc9.com>
> On 22.02.2023 22:34, Vladimir Oltean wrote:
> > The posted ethtool stats are not sufficient to determine the cause of
> > the issue. It would be necessary to see all non-zero Ethernet counters
> > on both CPU port pairs:
> >
> > ethtool -S eth0 | grep -v ': 0'
> > ethtool -S eth1 | grep -v ': 0'
> >
> > to determine whether the cause of the performance degradation is packet
> > loss or just a lossless slowdown of some sorts. For example, the
> > degradation might be caused by the added flow control + uncalibrated
> > watermarks, not by the activation of the other GMAC.
>
> I'll keep this in mind thanks.
>
> Frank, here's my task page for this issue, for your information.
>
> https://arinc9.notion.site/MT7530-port5-performance-issue-98ac5fa19dc248e0b12fab08dcb2e387
tried after adding the fix from daniel, but same issue, here the iperf and ethtool-results (does not look wrong except tx-speed)
root@...-r2:~# iperf3 -c 192.168.0.21
Connecting to host 192.168.0.21, port 5201
[ 5] local 192.168.0.11 port 36832 connected to 192.168.0.21 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 75.4 MBytes 633 Mbits/sec 0 361 KBytes
[ 5] 1.00-2.00 sec 74.4 MBytes 624 Mbits/sec 0 361 KBytes
[ 5] 2.00-3.00 sec 74.1 MBytes 622 Mbits/sec 0 361 KBytes
[ 5] 3.00-4.00 sec 74.2 MBytes 622 Mbits/sec 0 361 KBytes
[ 5] 4.00-5.00 sec 74.6 MBytes 626 Mbits/sec 0 361 KBytes
[ 5] 5.00-6.00 sec 74.4 MBytes 624 Mbits/sec 0 379 KBytes
[ 5] 6.00-7.00 sec 74.1 MBytes 621 Mbits/sec 0 379 KBytes
[ 5] 7.00-8.00 sec 74.7 MBytes 627 Mbits/sec 0 379 KBytes
[ 5] 8.00-9.00 sec 74.5 MBytes 625 Mbits/sec 0 564 KBytes
[ 5] 9.00-10.00 sec 74.3 MBytes 623 Mbits/sec 0 564 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 745 MBytes 625 Mbits/sec 0 sender
[ 5] 0.00-10.04 sec 744 MBytes 621 Mbits/sec receiver
iperf Done.
root@...-r2:~# iperf3 -c 192.168.0.21 -R
Connecting to host 192.168.0.21, port 5201
Reverse mode, remote host 192.168.0.21 is sending
[ 5] local 192.168.0.11 port 44428 connected to 192.168.0.21 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 112 MBytes 939 Mbits/sec
[ 5] 1.00-2.00 sec 112 MBytes 940 Mbits/sec
[ 5] 2.00-3.00 sec 112 MBytes 939 Mbits/sec
[ 5] 3.00-4.00 sec 112 MBytes 940 Mbits/sec
[ 5] 4.00-5.00 sec 112 MBytes 940 Mbits/sec
[ 5] 5.00-6.00 sec 112 MBytes 940 Mbits/sec
[ 5] 6.00-7.00 sec 112 MBytes 940 Mbits/sec
[ 5] 7.00-8.00 sec 112 MBytes 940 Mbits/sec
[ 5] 8.00-9.00 sec 112 MBytes 940 Mbits/sec
[ 5] 9.00-10.00 sec 112 MBytes 940 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.04 sec 1.10 GBytes 938 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 1.09 GBytes 940 Mbits/sec receiver
iperf Done.
root@...-r2:~# ethtool -S eth0 | grep -v ': 0'
NIC statistics:
tx_bytes: 1643364546
tx_packets: 1121377
rx_bytes: 1270088499
rx_packets: 1338400
p06_TxUnicast: 1338274
p06_TxMulticast: 120
p06_TxBroadcast: 6
p06_TxPktSz65To127: 525948
p06_TxPktSz128To255: 5
p06_TxPktSz256To511: 16
p06_TxPktSz512To1023: 4
p06_Tx1024ToMax: 812427
p06_TxBytes: 1275442099
p06_RxFiltering: 16
p06_RxUnicast: 1121339
p06_RxMulticast: 37
p06_RxBroadcast: 1
p06_RxPktSz64: 3
p06_RxPktSz65To127: 43757
p06_RxPktSz128To255: 3
p06_RxPktSz256To511: 3
p06_RxPktSz1024ToMax: 1077611
p06_RxBytes: 1643364546
root@...-r2:~# ethtool -S eth1 | grep -v ': 0'
NIC statistics:
root@...-r2:~#
breaking mt7531 as stated by vladimir is bad...currently afaik no other board uses second cpu-port (r2pro uses only port5, r3 uses port 5 as user-port for SFP).
if interested this is my tree:
https://github.com/frank-w/BPI-Router-Linux/tree/6.2-rc8-r2-dsa
regards Frank
Powered by blists - more mailing lists