vhost: add power monitor API

[dpdk.git] / doc / guides / sample_app_ug / ip_pipeline.rst

diff --git a/doc/guides/sample_app_ug/ip_pipeline.rst b/doc/guides/sample_app_ug/ip_pipeline.rst
index 56014be..b521d3b 100644 (file)
--- a/doc/guides/sample_app_ug/ip_pipeline.rst
+++ b/doc/guides/sample_app_ug/ip_pipeline.rst
@@ -34,7 +34,7 @@ Running the application
 
 The application startup command line is::
 
-   ip_pipeline [EAL_ARGS] -- [-s SCRIPT_FILE] [-h HOST] [-p PORT]
+   dpdk-ip_pipeline [EAL_ARGS] -- [-s SCRIPT_FILE] [-h HOST] [-p PORT]
 
 The application startup arguments are:
 
@@ -71,7 +71,7 @@ The following is an example command to run ip pipeline application configured fo
 
 .. code-block:: console
 
-    $ ./build/ip_pipeline -c 0x3 -- -s examples/route_ecmp.cli
+    $ ./<build_dir>/examples/dpdk-ip_pipeline -c 0x3 -- -s examples/route_ecmp.cli
 
 The application should start successfully and display as follows:
 
@@ -122,7 +122,7 @@ is displayed and the application is terminated.
 Run-time
 ~~~~~~~~
 
-The master thread is creating and managing all the application objects based on CLI input.
+The main thread is creating and managing all the application objects based on CLI input.
 
 Each data plane thread runs one or several pipelines previously assigned to it in round-robin order. Each data plane thread
 executes two tasks in time-sharing mode:
@@ -130,7 +130,7 @@ executes two tasks in time-sharing mode:
 1. *Packet processing task*: Process bursts of input packets read from the pipeline input ports.
 
 2. *Message handling task*: Periodically, the data plane thread pauses the packet processing task and polls for request
-   messages send by the master thread. Examples: add/remove pipeline to/from current data plane thread, add/delete rules
+   messages send by the main thread. Examples: add/remove pipeline to/from current data plane thread, add/delete rules
    to/from given table of a specific pipeline owned by the current data plane thread, read statistics, etc.
 
 Examples
@@ -253,11 +253,6 @@ Traffic manager
    <tc5_rate> <tc6_rate> <tc7_rate> <tc8_rate>
    <tc9_rate> <tc10_rate> <tc11_rate> <tc12_rate>
    <tc_period>
-   pps <n_pipes_per_subport>
-   qsize <qsize_tc0> <qsize_tc1> <qsize_tc2>
-   <qsize_tc3> <qsize_tc4> <qsize_tc5> <qsize_tc6>
-   <qsize_tc7> <qsize_tc8> <qsize_tc9> <qsize_tc10>
-   <qsize_tc11> <qsize_tc12>
 
  Add traffic manager pipe profile ::
 
@@ -275,6 +270,7 @@ Traffic manager
   tmgr <tmgr_name>
    rate <rate>
    spp <n_subports_per_port>
+   pps <n_pipes_per_subport>
    fo <frame_overhead>
    mtu <mtu>
    cpu <cpu_id>