doc: Update DPDK pdump documentation

The DPDK pdump sample app was renamed from 'dpdk_pdump' to
'dpdk-pdump'. Update references to same within
INSTALL.DPDK-ADVANCED.md.

Add an additional sample command line that shows how to capture all
traffic traversing an interface within a single pcap file - a useful
tool for debugging DPDK-related issues.

Signed-off-by: Mark Kavanagh <mark.b.kavanagh@intel.com>
Acked-by: Daniele Di Proietto <diproiettod@vmware.com>

diff --git a/INSTALL.DPDK-ADVANCED.md b/INSTALL.DPDK-ADVANCED.md
index 555f02640330fbd3fcd68983e8609ce5fdeaa383..f6f0b5bb5bd5247fa069c00b2e250a51bd6082d5 100644 (file)
--- a/INSTALL.DPDK-ADVANCED.md
+++ b/INSTALL.DPDK-ADVANCED.md
@@ -791,16 +791,24 @@ To use pdump, simply launch OVS as usual. Then, navigate to the 'app/pdump'
 directory in DPDK, 'make' the application and run like so:
 
 ```
-sudo ./build/app/dpdk_pdump --
+sudo ./build/app/dpdk-pdump --
 --pdump port=0,queue=0,rx-dev=/tmp/pkts.pcap
 --server-socket-path=/usr/local/var/run/openvswitch
 ```
 
 The above command captures traffic received on queue 0 of port 0 and stores
 it in /tmp/pkts.pcap. Other combinations of port numbers, queues numbers and
-pcap locations are of course also available to use. 'server-socket-path' must
-be set to the value of ovs_rundir() which typically resolves to
-'/usr/local/var/run/openvswitch'.
+pcap locations are of course also available to use. For example, to capture
+all packets that traverse port 0 in a single pcap file:
+
+```
+sudo ./build/app/dpdk-pdump --
+--pdump 'port=0,queue=*,rx-dev=/tmp/pkts.pcap,tx-dev=/tmp/pkts.pcap'
+--server-socket-path=/usr/local/var/run/openvswitch
+```
+
+'server-socket-path' must be set to the value of ovs_rundir() which typically
+resolves to '/usr/local/var/run/openvswitch'.
 More information on the pdump app and its usage can be found in the below link.
 
 http://dpdk.org/doc/guides/sample_app_ug/pdump.html