Re: dpdk-pdump cannot init tailq as secondary process

[Karim Harouat <ingenieur@ingenieur-high-tech.com>]

Hello

I'm using dpdk version 22.11 and so the arg --proc-type secondary is set 
hardcoded inside the dpdk-pdump main program.

I fixed my issue by taking all cflags in libdpdk.pc file linking any 
personnal application statically with all librte.

And so the static rte_fib tail is initialized properly for the 
dpdk-pdump. But my app is bigger now, I'm currently trying to link only 
needed libraries to reduce the size.

With less libraries static linkage now I am facing with another issue,  
it is create ring vdev function which failed.

I will try dpdk-dumpcap

Thank you!

Le 24/04/2023 à 18:17, Stephen Hemminger a écrit :
> On Thu, 20 Apr 2023 12:18:15 +0000
> postmaster <postmaster@ingenieur-high-tech.com> wrote:
>
>> Hello
>>
>> I follow what it is explained on that page
>>
>> https://doc.dpdk.org/guides/tools/pdump.html
>>
>> to call rte_pdump_init in my application (and checking the result, if not ok exit with failure), but once I ran dpdk-pdump I got
>>
>>
>> dpdk-pdump  -l 9 -- --pdump 'port=0,queue=*,rx-dev=/tmp/rx.pcap'
>> EAL: Detected CPU lcores: 24
>> EAL: Detected NUMA nodes: 1
>> EAL: Detected static linkage of DPDK
>> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_1027261_2ca45105bcf34
>> EAL: Selected IOVA mode 'PA'
>> EAL: VFIO support initialized
>> EAL: Cannot initialize tailq: RTE_FIB
> Looks like pdump is not being run as a secondary process.
> Try adding --proc-type secondary
>
> Also, pdump is legacy application; please try dpdk-dumpcap instead.
> Dumpcap supports more information, multiple interfaces, etc.
>