Not to be fixed
Created: Oct 22, 2019
Updated: Apr 29, 2021
Resolved Date: Apr 29, 2021
Found In Version: 10.19.45.1
Severity: Standard
Applicable for: Wind River Linux LTS 19
Component/s: BSP
1. Deploy testing environment, see NetTopology.png
2. build
RT project
setup.sh --machines intel-x86-64 --templates feature/dpdk,feature/bsp-extras --distro wrlinux --layer meta-dpdk --dl-layers
Set PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"
bitbake wrlinux-image-std
Standard project
--machines intel-x86-64 --templates feature/dpdk,feature/bsp-extras --distro wrlinux --layer meta-dpdk --dl-layers
bitbake wrlinux-image-std
OV project
--machines intel-x86-64 --templates feature/dpdk,feature/bsp-extras --distro wrlinux-ovp --layer meta-dpdk --dl-layers
Set PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"
bitbake wrlinux-image-ovp-kvm
3. boot 2 Harcuvar targets (24977 as client, 24976 as server)
kernel console=ttyS0,115200n8 root=/dev/nfs rw nfsroot=<server-ip>/path/to/rootfs,v3,tcp ip=dhcp ignore_loglevel selinux=0 enforcing=0 noinitrd intel_iommu=on memtest=0 kmemleak=off
4. Set iperf3 server side
ip addr del 192.168.1.21/24 dev eth1
ip link set eth1 up
ip link set dev eth1 mtu 9000
ip addr add 192.168.1.21/24 dev eth1
iperf3 -sD
5. Run iperf3 client by TCP
ip addr del 192.168.1.11/24 dev eth1
ip link set eth1 up
ip link set dev eth1 mtu $MTU
ip addr add 192.168.1.11/24 dev eth1
ip addr show eth1
iperf3 -c 192.168.1.21 -t 600 -i 60 -P10 -O 10 -Z --logfile /opt/wr-test/testcases/benchmark/iperf3/iperf3_tcp_$MTU.log
6. Run iperf3 client by UDP
ip addr del 192.168.1.11/24 dev eth1
ip link set eth1 up
ip link set dev eth1 mtu $MTU
ip addr add 192.168.1.11/24 dev eth1
ip addr show eth1
iperf3 -u -c 192.168.1.21 -t 600 -i 60 -P10 -O 10 -Z -b ${bandwidth} --logfile /opt/wr-test/testcases/benchmark/iperf3/iperf3_udp_$MTU_${bandwidth}.log
7. Check results using the different $MTU (1024, 1500, 9000) and $bandwidth (0, 105m, 1000m), See
iperf3_comparison_UDP.xlsx
iperf3_comparison_TCP.xlsx
8. Can obtain the same comparison results with release version 10.19.41.0/10.19.42.0/10.19.43.0
We can tell that bandwidth of wrlinux-ovp is lower than wrlinux from the following spreadsheet or log:
See comparison results in iperf3_comparison_UDP.xlsx and iperf3_comparison_TCP.xlsx
See detail steps in iperf3.log
See test environment in NetTopology.png
[^iperf3_comparison_TCP.xlsx] [^iperf3_comparison_UDP.xlsx] [^iperf3.log] !NetTopology.png|thumbnail!
1. Deploy testing environment, see NetTopology.png
2. build
RT project
--machines intel-x86-64 --templates feature/dpdk,feature/bsp-extras --distro wrlinux --layer meta-dpdk --dl-layers
Set PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"
bitbake wrlinux-image-std
Standard project
--machines intel-x86-64 --templates feature/dpdk,feature/bsp-extras --distro wrlinux --layer meta-dpdk --dl-layers
bitbake wrlinux-image-std
OV project
--machines intel-x86-64 --templates feature/dpdk,feature/bsp-extras --distro wrlinux-ovp --layer meta-dpdk --dl-layers
Set PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"
bitbake wrlinux-image-ovp-kvm
3. boot 2 Harcuvar targets (24977 as client, 24976 as server)
kernel console=ttyS0,115200n8 root=/dev/nfs rw nfsroot=128.224.165.20:/export/pxeboot/vlm-boards/24977(or 24976)/rootfs,v3,tcp ip=dhcp ignore_loglevel selinux=0 enforcing=0 noinitrd intel_iommu=on memtest=0 kmemleak=off
4. Set iperf3 server side
ip addr del 192.168.1.21/24 dev eth1
ip link set eth1 up
ip link set dev eth1 mtu 9000
ip addr add 192.168.1.21/24 dev eth1
iperf3 -sD
5. Run iperf3 client by TCP
ip addr del 192.168.1.11/24 dev eth1
ip link set eth1 up
ip link set dev eth1 mtu $MTU
ip addr add 192.168.1.11/24 dev eth1
ip addr show eth1
iperf3 -c 192.168.1.21 -t 600 -i 60 -P10 -O 10 -Z --logfile /opt/wr-test/testcases/benchmark/iperf3/iperf3_tcp_$MTU.log
6. Run iperf3 client by UDP
ip addr del 192.168.1.11/24 dev eth1
ip link set eth1 up
ip link set dev eth1 mtu $MTU
ip addr add 192.168.1.11/24 dev eth1
ip addr show eth1
iperf3 -u -c 192.168.1.21 -t 600 -i 60 -P10 -O 10 -Z -b ${bandwidth} --logfile /opt/wr-test/testcases/benchmark/iperf3/iperf3_udp_$MTU_${bandwidth}.log
7. Check results using the different $MTU (1024, 1500, 9000) and $bandwidth (0, 105m, 1000m), See
iperf3_comparison_UDP.xlsx
iperf3_comparison_TCP.xlsx
8. Can obtain the same comparison results with release version 10.19.41.0/10.19.42.0/10.19.43.0
