DPDK usage discussions
 help / color / mirror / Atom feed
From: Karim Harouat <ingenieur@ingenieur-high-tech.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: dpdk-pdump cannot init tailq as secondary process
Date: Tue, 25 Apr 2023 08:08:09 +0200	[thread overview]
Message-ID: <2601f487-3355-3443-12bf-f8a1fa7ef392@ingenieur-high-tech.com> (raw)
In-Reply-To: <20230424091750.7a045c4c@hermes.local>

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.
>

      reply	other threads:[~2023-04-27  7:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20 12:18 postmaster
2023-04-24 16:17 ` Stephen Hemminger
2023-04-25  6:08   ` Karim Harouat [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2601f487-3355-3443-12bf-f8a1fa7ef392@ingenieur-high-tech.com \
    --to=ingenieur@ingenieur-high-tech.com \
    --cc=stephen@networkplumber.org \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).