Hi, > -----Original Message----- > From: Pavel Fedin [mailto:p.fedin at samsung.com] > Sent: Thursday, February 18, 2016 2:08 PM > To: Pattan, Reshma <reshma.pattan at intel.com>; dev at dpdk.org > Subject: RE: [dpdk-dev] [PATCH v2 0/5] add dpdk packet capture support for > tcpdump > > > 1. Perhaps, ability to separate queues is useful for something. But not > always. > For example, what if i want to capture all the traffic which passes through > some > interface (common use case)? For example, with OpenVSwitch i can have 9 > queues on my networking card. So, i have to enumerate all of them: > (0,0)(0,1)(0,2)... It's insane and inconvenient with many queues. What if you > could have shorthand notation, like (0) or (0,*) for this?
I will fix this in my next version of patch. > 2. What if i don't want separate RX and TX streams either? It only prevents > me > from seeing the complete picture. Do you mean not to have separate pcap files for tx and rx? If so, I would prefer to keep this as it is. Because pcap changes need to be replaced with TUN/TAP pmd once available in future. > 3. vhostuser ports are missing. Perhaps not really related to this patchset, > i just > don't know how much code "server" part of vhostuser shares with normal PMDs, > but anyway, ability to dump them too would be nice to have. > I think this can be done in future i.e. when vhost as PMD is available. But as of now vhost is library. > Not directly related, but could we have some interface to tcpdump or > wireshark? Would be good to have ability to dump packets in real time. This can be done in future once KNI or TUN/TAP PMDs is available in DPDK. Thanks, Reshma
