User Manual

TRex 83 / 113
[bash]>sudo ./dpdk_nic_bind.py -s
Network devices using DPDK-compatible driver
============================================
0000:03:10.0 ’82599 Ethernet Controller Virtual Function’ drv=igb_uio unused=
0000:03:10.1 ’82599 Ethernet Controller Virtual Function’ drv=igb_uio unused=
Network devices using kernel driver
===================================
0000:01:00.0 ’I350 Gigabit Network Connection’ if=eth0 drv=igb unused=igb_uio
*
Active
*
0000:03:00.0 ’82599ES 10-Gigabit SFI/SFP+ Network Connection’ if=eth2 drv=ixgbe unused= ←-
igb_uio
0000:03:00.1 ’82599ES 10-Gigabit SFI/SFP+ Network Connection’ if=eth3 drv=ixgbe unused= ←-
igb_uio
In order to work with 0000:03:10.0 and 0000:03:10.1, you will have to run the following
[bash]>sudo ifconfig eth3 up mtu 9000
[bash]>sudo ifconfig eth2 up mtu 9000
TRex stateful performance
Using the following command, running on x710 card with VF driver, we can see that TRex can reach 30GBps, using only
one core. We can also see that the average latency is around 20 usec, which is pretty much the same value we get on
loopback ports with x710 physical function without VF.
[bash]>sudo ./t-rex-64 -f cap2/http_simple.yaml -m 40000 -l 100 -c 1 -p
[bash]>sudo ./t-rex-64 -f cap2/http_simple.yaml -m 40000 -l 100 -c 1 -p
-Per port stats table
ports | 0 | 1
-----------------------------------------------------------------------------------------
opackets | 106573954 | 107433792
obytes | 99570878833 | 100374254956
ipackets | 107413075 | 106594490
ibytes | 100354899813 | 99590070585
ierrors | 1038 | 1027
oerrors | 0 | 0
Tx Bw | 15.33 Gbps | 15.45 Gbps
-Global stats enabled
Cpu Utilization : 91.5 % 67.3 Gb/core
Platform_factor : 1.0
Total-Tx : 30.79 Gbps
Total-Rx : 30.79 Gbps
Total-PPS : 4.12 Mpps
Total-CPS : 111.32 Kcps
Expected-PPS : 4.11 Mpps
Expected-CPS : 111.04 Kcps
Expected-BPS : 30.71 Gbps
Active-flows : 14651 Clients : 255 Socket-util : 0.0912 %
Open-flows : 5795073 Servers : 65535 Socket : 14652 Socket/Clients : 57.5
drop-rate : 0.00 bps
current time : 53.9 sec
test duration : 3546.1 sec
-Latency stats enabled