Re: [dpdk-dev] [PATCH v2 0/5] add dpdk packet capture support for tcpdump

[Pavel Fedin <p.fedin@samsung.com>]

 Hello!

 With the aforementioned fix (disabling src_ip_filter  if zero) i've got the patch series working. Now i have some more notes on
usability:

> 2)Start proc_info(runs as secondary process by default)application with new parameters for
> tcpdump.
> ex: sudo ./build/app/proc_info/dpdk_proc_info -c 0x4 -n 2 -- -p 0x3 --tcpdump '(0,0)(1,0)' --
> src-ip-filter="2.2.2.2"

 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?
 2. What if i don't want separate RX and TX streams either? It only prevents me from seeing the complete picture.
 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.

 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.

Kind regards,
Pavel Fedin
Senior Engineer
Samsung Electronics Research center Russia