X-Git-Url: https://gerrit.fd.io/r/gitweb?a=blobdiff_plain;f=docs%2Freport%2Fintroduction%2Fmethodology_trex_traffic_generator.rst;h=918a34f73deab35c9a5628e38b8f46b0447657ab;hb=6aeb3f1bbbda53855f9b0c9148c7e60201502e05;hp=4d4de96fb010a2854ff5c23a5eeda8d2bae71bca;hpb=124101d22151239b0411a73ae4d2bf8d70970937;p=csit.git

diff --git a/docs/report/introduction/methodology_trex_traffic_generator.rst b/docs/report/introduction/methodology_trex_traffic_generator.rst
index 4d4de96fb0..918a34f73d 100644
--- a/docs/report/introduction/methodology_trex_traffic_generator.rst
+++ b/docs/report/introduction/methodology_trex_traffic_generator.rst
@@ -6,9 +6,8 @@ Usage
 
 `TRex traffic generator <https://wiki.fd.io/view/TRex>`_ is used for all
 CSIT performance tests. TRex stateless mode is used to measure NDR and
-PDR throughputs using binary search (NDR and PDR discovery tests) and
-for quick checks of DUT performance against the reference NDRs (NDR
-check tests) for specific configuration.
+PDR throughputs using MLRsearch and to measure maximum transer rate
+in MRR tests.
 
 TRex is installed and run on the TG compute node. The typical procedure
 is:
@@ -23,11 +22,11 @@ is:
 - TRex is started in the background mode
   ::
 
-  $ sh -c 'cd <t-rex-install-dir>/scripts/ && sudo nohup ./t-rex-64 -i -c 7 --iom 0 > /tmp/trex.log 2>&1 &' > /dev/null
+  $ sh -c 'cd <t-rex-install-dir>/scripts/ && sudo nohup ./t-rex-64 -i -c 7  > /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
-  :command:`trex_stl_lib.api.STLClient`.
+  :command:`trex.stl.api.STLClient`.
 
 Measuring Packet Loss
 ~~~~~~~~~~~~~~~~~~~~~