2016-06-14 10:38, Reshma Pattan: > New tool added for packet capturing on dpdk. > This tool supports command line options. > This tool runs as secondary process by default. > > Command line supports various parameters to capture > the packets. > > User should pass on a)port and queue (or) b)pci address > and queue (or) c)device name and queue to capture > the packets. > > Users also need to pass on either pcap file name or > any linux iface, on to which packets captured from dpdk > ports will be sent on for the users to view using tcpdump. > > Users have option to capture packets either a) in Rx > direction, b)(or) in Tx direction c)(or) from both the > directions. > > User can pass on ring_size and mempool parameters using > command line, but these are optional parameters. > These are used to create ring and mempool objects for packet > mirroring from primary application to tool. If user doesn't > provide any values, default values will be used internally > for the creation of the ring and mempool.
The explanations should be in an user guide. > --- a/app/Makefile > +++ b/app/Makefile > @@ -37,5 +37,6 @@ DIRS-$(CONFIG_RTE_LIBRTE_PIPELINE) += test-pipeline > DIRS-$(CONFIG_RTE_TEST_PMD) += test-pmd > DIRS-$(CONFIG_RTE_LIBRTE_CMDLINE) += cmdline_test > DIRS-$(CONFIG_RTE_EXEC_ENV_LINUXAPP) += proc_info > +DIRS-$(CONFIG_RTE_EXEC_ENV_LINUXAPP) += pdump Why Linux only? There is a build error if CONFIG_RTE_LIBRTE_PDUMP is disabled.