Hi Team,
What is the command and test bench on test PRU_ICSSG Ethernet throughput?
The ICSSG UDP Egress throughput is only 94.21Mbps,
While CPSW UDP Egress is as expected as 914Mbps
Could you clarify?
-Thomas
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi Team,
What is the command and test bench on test PRU_ICSSG Ethernet throughput?
The ICSSG UDP Egress throughput is only 94.21Mbps,
While CPSW UDP Egress is as expected as 914Mbps
Could you clarify?
-Thomas
Hello Thomas,
The commands to test the UDP throughput should be thoroughly documented here: https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/08_04_01_04/exports/docs/devices/AM64X/RT_Linux_Performance_Guide.html#ethernet
I agree that less than 100Mbit throughput does not make sense if the PRU_ICSSG Ethernet was tested on a gigabit link. Do you have an EVM to run tests? If not I can try it out later this week.
Regards,
Nick
Hi Nick,
We used iperf to test AM64x PRU ICSSG Ethernet TCP is 800~900Mbps, and UDP 400M(%0 loss)~600M(<1% loss), but Linux SDK doc show PRU ICSSG performance is much poor (90Mbps), please help clarify to avoid customer confuse.
-Thomas
Hello Thomas,
I see similar results using netperf (reported throughput of 720 Mbits for UDP egress tests). I'll file a ticket against the documentation and double-check on the testing methodology.
root@am64xx-evm:~# ifconfig eth2 down [ 159.611999] icssg-prueth icssg1-eth eth2: Link is Down [ 159.623599] remoteproc remoteproc13: stopped remote processor 3008a000.txpru [ 159.630865] remoteproc remoteproc12: stopped remote processor 30084000.rtu [ 159.638909] remoteproc remoteproc11: stopped remote processor 300b4000.pru [ 159.647210] net eth2: stopped root@am64xx-evm:~# ifconfig eth2 192.168.1.167 ... root@am64xx-evm:~# [ 176.104359] icssg-prueth icssg1-eth eth2: Link is Up - 1Gbps/Full - flow control off [ 176.112163] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready root@am64xx-evm:~# netperf -H 192.168.1.100 -j -c -l 60 -t UDP_STREAM -- -m 1470 -k DIRECTION,T HROUGHPUT,MEAN_LATENCY,LOCAL_CPU_UTIL,REMOTE_CPU_UTIL,LOCAL_BYTES_SENT,REMOTE_BYTES_RECVD,LOCAL _SEND_SIZE MIGRATED UDP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.1.100 () port 0 AF_IN ET : histogram : interval DIRECTION=Send THROUGHPUT=720.60 MEAN_LATENCY=16.03 LOCAL_CPU_UTIL=62.44 REMOTE_CPU_UTIL=-1.00 LOCAL_BYTES_SENT=5404575540 REMOTE_BYTES_RECVD=5404575540 LOCAL_SEND_SIZE=1470
Thanks for reporting,
Nick