The testpmd DPDK application has been renamed to dpdk-testpmd a while
ago. Use the dpdk-testpmd wording in all documentation.

Also fix a reference to a "make" build directory.

Signed-off-by: David Marchand <[email protected]>
---
 Documentation/howto/dpdk.rst             | 9 +++++----
 Documentation/intro/install/dpdk.rst     | 2 +-
 Documentation/topics/dpdk/vhost-user.rst | 9 ++++-----
 3 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/Documentation/howto/dpdk.rst b/Documentation/howto/dpdk.rst
index 40a7e8fd8b..2c4d2d2eef 100644
--- a/Documentation/howto/dpdk.rst
+++ b/Documentation/howto/dpdk.rst
@@ -217,11 +217,11 @@ For a explanation of this command, along with alternative 
approaches such as
 booting the VM via libvirt, refer to :doc:`/topics/dpdk/vhost-user`.
 
 Once the guest is configured and booted, configure DPDK packet forwarding
-within the guest. To accomplish this, build the ``testpmd`` application as
+within the guest. To accomplish this, build the ``dpdk-testpmd`` application as
 described in :ref:`dpdk-testpmd`. Once compiled, run the application::
 
-    $ cd $DPDK_DIR/app/test-pmd;
-    $ ./testpmd -c 0x3 -n 4 --socket-mem 1024 -- \
+    $ cd /path/to/dpdk/build/
+    $ ./dpdk-testpmd -c 0x3 -n 4 --socket-mem 1024 -- \
         --burst=64 -i --txqflags=0xf00 --disable-hw-vlan
     $ set fwd mac retry
     $ start
@@ -247,7 +247,8 @@ PHY-VM-PHY (vHost Loopback) (Kernel Forwarding)
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 :ref:`dpdk-vhost-loopback` details steps for PHY-VM-PHY loopback
-testcase and packet forwarding using DPDK testpmd application in the Guest VM.
+testcase and packet forwarding using the ``dpdk-testpmd`` application in the
+Guest VM.
 For users wishing to do packet forwarding using kernel stack below, you need to
 run the below commands on the guest::
 
diff --git a/Documentation/intro/install/dpdk.rst 
b/Documentation/intro/install/dpdk.rst
index 47d79335b2..2d97149c46 100644
--- a/Documentation/intro/install/dpdk.rst
+++ b/Documentation/intro/install/dpdk.rst
@@ -542,7 +542,7 @@ have affinity set accordingly.
   occupancy as possible.
 
   For example, on a multicore VM, multiple QEMU vCPU threads shall be spawned.
-  When the DPDK ``testpmd`` application that does packet forwarding is invoked,
+  When the ``dpdk-testpmd`` application that does packet forwarding is invoked,
   the ``taskset`` command should be used to affinitize the vCPU threads to the
   dedicated isolated cores on the host system.
 
diff --git a/Documentation/topics/dpdk/vhost-user.rst 
b/Documentation/topics/dpdk/vhost-user.rst
index 3c31f52000..52bbfeb32f 100644
--- a/Documentation/topics/dpdk/vhost-user.rst
+++ b/Documentation/topics/dpdk/vhost-user.rst
@@ -395,10 +395,9 @@ Maximum number of queue pairs can be set for 
vhost-user-client-ports::
 DPDK in the Guest
 -----------------
 
-The DPDK ``testpmd`` application can be run in guest VMs for high speed packet
-forwarding between vhostuser ports. DPDK and testpmd application has to be
-compiled on the guest VM. Below are the steps for setting up the testpmd
-application in the VM.
+The ``dpdk-testpmd`` application can be run in guest VMs for high speed packet
+forwarding between vhostuser ports. DPDK has to be compiled on the guest VM.
+Below are the steps for setting up the environment in the VM.
 
 .. note::
 
@@ -540,7 +539,7 @@ introduced in QEMU 2.7.0 / libvirt 2.3.0::
   </interface>
 
 The guest application will also need to provide enough descriptors.
-For example with ``testpmd`` the command line argument can be used::
+For example with ``dpdk-testpmd`` the command line argument can be used::
 
  --rxd=1024 --txd=1024
 
-- 
2.49.0

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to