User Manual

TRex 66 / 113
traffic_mbuf_64 : 16380
v
3
traffic_mbuf_128 : 8190
traffic_mbuf_256 : 8190
traffic_mbuf_512 : 8190
traffic_mbuf_1024 : 8190
traffic_mbuf_2048 : 4096
dp_flows : 1048576
v
4
global_flows : 10240
v
5
v
1
Memory section header
v
2
Numbers of memory buffers allocated for packets in transit, per port pair. Numbers are specified per packet size.
v
3
Numbers of memory buffers allocated for holding the part of the packet which is remained unchanged per template. You
should increase numbers here, only if you have very large amount of templates.
v
4
Number of TRex flow objects allocated (To get best performance they are allocated upfront, and not dynamically). If you
expect more concurrent flows than the default (1048576), enlarge this.
v
5
Number objects TRex allocates for holding NAT “in transit” connections. In stateful mode, TRex learn NAT translation
by looking at the address changes done by the DUT to the first packet of each flow. So, these are the number of flows for
which TRex sent the first flow packet, but did not learn the translation yet. Again, default here (10240) should be good.
Increase only if you use NAT and see issues.
6.2.3 Platform section configuration
The platform section is optional. It is used to tune the performance and allocate the cores to the right NUMA a configuration file
now has the folowing struct to support multi instance
- version : 2
interfaces : ["03:00.0","03:00.1"]
port_limit : 2
....
platform :
v
1
master_thread_id : 0
v
2
latency_thread_id : 5
v
3
dual_if :
v
4
- socket : 0
v
5
threads : [1,2,3,4]
v
6
v
1
Platform section header.
v
2
Hardware thread_id for control thread.
v
3
Hardware thread_id for RX thread.
v
4
“dual_if” section defines info for interface pairs (according to the order in “interfaces” list). each section, starting with “-
socket” defines info for different interface pair.
v
5
The NUMA node from which memory will be allocated for use by the interface pair.
v
6
Hardware threads to be used for sending packets for the interface pair. Threads are pinned to cores, so specifying threads
actually determines the hardware cores.
Real example:
We connected 2 Intel XL710 NICs close to each other on the motherboard. They shared the same NUMA: