User Manual

TRex 60 / 113
This feature ensures that:
• Packets get out of DUT in order (from each flow perspective).
• There are no packet drops (no need to wait for the end of the test). Without this flag, you must wait for the end of the test in
order to identify packet drops, because there is always a difference between TX and Rx, due to RTT.
Full example
[bash]>sudo ./t-rex-64 -f avl/sfr_delay_10_1g.yaml -c 4 -p -l 100 -d 100000 -m 30 --rx- ←-
check 128
Cpu Utilization : 0.1 % ←-
v
1
if| tx_ok , rx_ok , rx ,error, average , max , Jitter , max window
| , , check, , latency(usec),latency (usec) ,(usec) ,
--------------------------------------------------------------------------------
0 | 1002, 1002, 2501, 0, 61 , 70, 3 | 60
1 | 1002, 1002, 2012, 0, 56 , 63, 2 | 50
2 | 1002, 1002, 2322, 0, 66 , 74, 5 | 68
3 | 1002, 1002, 1727, 0, 58 , 68, 2 | 52
Rx Check stats enabled ←-
v
2
←-
------------------------------------------------------------------------------------------- ←-
rx check: avg/max/jitter latency, 94 , 744, 49 | 252 287 309 ←-
v
3
active flows:
v
4
10, fif:
v
5
308, drop: 0, errors: 0
v
6
←-
------------------------------------------------------------------------------------------- ←-
v
1
CPU% of the Rx thread. If it is too high, increase the sample rate.
v
2
Rx Check section. For more detailed info, press r during the test or at the end of the test.
v
3
Average latency, max latency, jitter on the template flows in microseconds. This is usually higher than the latency check
packet because the feature works more on this packet.
v
6
Drop counters and errors counter should be zero. If not, press r to see the full report or view the report at the end of the
test.
v
5
fif - First in flow. Number of new flows handled by the Rx thread.
v
4
active flows - number of active flows handled by rx thread
Press R to Display Full Report
m_total_rx : 2
m_lookup : 2
m_found : 1
m_fif : 1
m_add : 1
m_remove : 1
m_active : 0
v
1
0 0 0 0 1041 0 0 0 0 0 0 0 0 min_delta : 10 usec
cnt : 2