aboutsummaryrefslogtreecommitdiffstats
path: root/docs/report
diff options
context:
space:
mode:
Diffstat (limited to 'docs/report')
-rw-r--r--docs/report/introduction/methodology_trex_traffic_generator.rst42
1 files changed, 22 insertions, 20 deletions
diff --git a/docs/report/introduction/methodology_trex_traffic_generator.rst b/docs/report/introduction/methodology_trex_traffic_generator.rst
index cae65ab1c8..dfa496b3ad 100644
--- a/docs/report/introduction/methodology_trex_traffic_generator.rst
+++ b/docs/report/introduction/methodology_trex_traffic_generator.rst
@@ -11,32 +11,34 @@ throughputs using MLRsearch and to measure maximum transfer rate in MRR tests.
TRex is installed and run on the TG compute node. The typical procedure is:
- TRex configuration is set in its configuration file
+
::
- $ sudo -E -S sh -c 'cat << EOF > /etc/trex_cfg.yaml
- - version: 2
- c: 15
- limit_memory: 8192
- interfaces: ["${pci1}","${pci2}"]
- port_info:
- - dest_mac: [${dest_mac1}]
- src_mac: [${src_mac1}]
- - dest_mac: [${dest_mac2}]
- src_mac: [${src_mac2}]
- platform :
- master_thread_id: 0
- latency_thread_id: 16
- dual_if:
- - socket: 0
- threads: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15]
- EOF'
+ $ sudo -E -S sh -c 'cat << EOF > /etc/trex_cfg.yaml
+ - version: 2
+ c: 15
+ limit_memory: 8192
+ interfaces: ["${pci1}","${pci2}"]
+ port_info:
+ - dest_mac: [${dest_mac1}]
+ src_mac: [${src_mac1}]
+ - dest_mac: [${dest_mac2}]
+ src_mac: [${src_mac2}]
+ platform :
+ master_thread_id: 0
+ latency_thread_id: 16
+ dual_if:
+ - socket: 0
+ threads: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15]
+ EOF'
- TRex is started in the interactive mode as a background service
+
::
- $ sh -c 'cd <t-rex-install-dir>/scripts/ && \
- sudo nohup ./t-rex-64 -i --prefix $(hostname) --hdrh --no-scapy-server \
- > /tmp/trex.log 2>&1 &' > /dev/null
+ $ sh -c 'cd <t-rex-install-dir>/scripts/ && \
+ sudo nohup ./t-rex-64 -i --prefix $(hostname) --hdrh --no-scapy-server \
+ > /tmp/trex.log 2>&1 &' > /dev/null
- There are traffic streams dynamically prepared for each test, based on traffic
profiles. The traffic is sent and the statistics obtained using API