2016-08-10 8:53 GMT-07:00 Aaron Conole <acon...@redhat.com>: > Ciara Loftus <ciara.lof...@intel.com> writes: > > > This commit provides the ability to 'listen' on DPDK ports and save > > packets to a pcap file with a DPDK app that uses the librte_pdump > > library. One such app is the 'pdump' app that can be found in the DPDK > > 'app' directory. Instructions on how to use this can be found in > > INSTALL.DPDK-ADVANCED.md > > > > Pdump capability in OVS with DPDK will only be initialised if the > > CONFIG_RTE_LIBRTE_PMD_PCAP=y and CONFIG_RTE_LIBRTE_PDUMP=y options are > > set in DPDK. libpcap is required if the above configuration is used. > > > > Signed-off-by: Ciara Loftus <ciara.lof...@intel.com> > > --- > > Hi Ciara, > > I haven't reviewed this patch, but am planning on it. Is there a reason > not to use the ovs mirroring facility in favor of pdump? Do you have > any metrics to share? Curious, because I've used the ovs mirror for > dpdk ports (including bonds), and it worked fine for me (but I never > tested for the perfomance impact). > > Would it make sense to mention that as well in the documentation? > > -Aaron >
Hi Aaron, I think both facilities are useful. This is more low level and it works independently of the OVS datapath, so it could be used to debug classification issue but requires a non default compile time flag in DPDK. ovs-tcpdump is more immediate to use and it's better integrated with tcpdump but works on top of OVS datapath and translation layer. I think it would be helpful to mention ovs-tcpdump in the documentation. For the moment I just pushed this to master, with a minor style change. Thanks, Daniele _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
