DPDK usage discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: dpdk-dumpcap
Date: Mon, 8 Jul 2024 10:27:33 +0200	[thread overview]
Message-ID: <CAJFAV8zZw1n9A_rqej8zSeAE5tZkntC1RSA8ywh5Ozvfn3Hdcw@mail.gmail.com> (raw)
In-Reply-To: <CH3PR01MB8470AEF2AA6BF0ABE22FABCA8FD92@CH3PR01MB8470.prod.exchangelabs.com>

On Sun, Jul 7, 2024 at 10:59 PM Lombardo, Ed <Ed.Lombardo@netscout.com> wrote:
>
> Hi,
> I am looking to debug my issue with dpdk and E810 NIC for transmit with GRE header.  The dpdk-dumpcap utility is my focus to see what dpdk is transmitting.  I have carefully studied the mbufs for the packet and looks correct.
> I built dpdk-dumpcap utility with debug enabled in meson in dpdk.22.11 and copied dpdk-dumpcap to the VM running our application.
> Our application is using the same version of dpdk 22.11 and built with static libraries. Also rebuilt our application with the EAL argument of “proc-type=primary”.
> When I run dpdk-dumpcap I get errors for RTE_FIB tailq.  I don’t understand this error, why tailq for RTE_FIB is not created in the dpdk-dumpcap application.  Do I need the RTE_FIB for packet capture, can I bypass the need for RTE_FIB?
>
> EAL: Cannot initialize tailq: RTE_FIB
> Tailq 0: qname:<RTE_DIST_BURST>, tqh_first:(nil), tqh_last:0x100000198
> Tailq 1: qname:<RTE_DISTRIBUTOR>, tqh_first:(nil), tqh_last:0x1000001c8
> Tailq 2: qname:<RTE_REORDER>, tqh_first:(nil), tqh_last:0x1000001f8
> Tailq 3: qname:<RTE_SWX_PIPELINE>, tqh_first:(nil), tqh_last:0x100000228
> Tailq 4: qname:<RTE_SWX_CTL_PIPELINE>, tqh_first:(nil), tqh_last:0x100000258
> Tailq 5: qname:<RTE_HASH>, tqh_first:(nil), tqh_last:0x100000288
> Tailq 6: qname:<RTE_FBK_HASH>, tqh_first:(nil), tqh_last:0x1000002b8
> Tailq 7: qname:<RTE_THASH>, tqh_first:(nil), tqh_last:0x1000002e8
> Tailq 8: qname:<RTE_LPM>, tqh_first:(nil), tqh_last:0x100000318
> Tailq 9: qname:<RTE_LPM6>, tqh_first:(nil), tqh_last:0x100000348
> Tailq 10: qname:<RTE_ACL>, tqh_first:(nil), tqh_last:0x100000378
> Tailq 11: qname:<RTE_MEMPOOL>, tqh_first:0x1bff3b580, tqh_last:0x1bff3b580
> Tailq 12: qname:<RTE_RING>, tqh_first:0x1bff3b4c0, tqh_last:0x1bff41f40
> Tailq 13: qname:<RTE_MBUF_DYNFIELD>, tqh_first:0x1bff3b800, tqh_last:0x1504000c0
> Tailq 14: qname:<RTE_MBUF_DYNFLAG>, tqh_first:(nil), tqh_last:0x100000438
> Tailq 15: qname:<UIO_RESOURCE_LIST>, tqh_first:0x1bffd8dc0, tqh_last:0x1bff37dc0
> Tailq 16: qname:<VFIO_RESOURCE_LIST>, tqh_first:(nil), tqh_last:0x100000498
> Tailq 17: qname:<>, tqh_first:(nil), tqh_last:(nil)
> Tailq 18: qname:<>, tqh_first:(nil), tqh_last:(nil)
> Tailq 19: qname:<>, tqh_first:(nil), tqh_last:(nil)
> Tailq 20: qname:<>, tqh_first:(nil), tqh_last:(nil)
> Tailq 21: qname:<>, tqh_first:(nil), tqh_last:(nil)
> Tailq 22: qname:<>, tqh_first:(nil), tqh_last:(nil)
> Tailq 23: qname:<>, tqh_first:(nil), tqh_last:(nil)
> Tailq 24: qname:<>, tqh_first:(nil), tqh_last:(nil)
> Tailq 25: qname:<>, tqh_first:(nil), tqh_last:(nil)
> Tailq 26: qname:<>, tqh_first:(nil), tqh_last:(nil)
> Tailq 27: qname:<>, tqh_first:(nil), tqh_last:(nil)
> Tailq 28: qname:<>, tqh_first:(nil), tqh_last:(nil)
> Tailq 29: qname:<>, tqh_first:(nil), tqh_last:(nil)
> Tailq 30: qname:<>, tqh_first:(nil), tqh_last:(nil)
> Tailq 31: qname:<>, tqh_first:(nil), tqh_last:(nil)
> EAL: FATAL: Cannot init tail queues for objects
> EAL: Cannot init tail queues for objects
> EAL: Error - exiting with code: 1
>   Cause: EAL init failed: is primary process running?

This means that the primary process binary (your application) does not
have the FIB library builtin.
Since v22.11, I see no fix in main that could explain this.

Did you perhaps link your application manually? (I mean, not using pkg-config)


-- 
David Marchand


  parent reply	other threads:[~2024-07-08  8:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-07 20:58 dpdk-dumpcap Lombardo, Ed
2024-07-07 21:11 ` dpdk-dumpcap Stephen Hemminger
2024-07-08  8:27 ` David Marchand [this message]
2024-07-09  3:53   ` dpdk-dumpcap Lombardo, Ed

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=CAJFAV8zZw1n9A_rqej8zSeAE5tZkntC1RSA8ywh5Ozvfn3Hdcw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=Ed.Lombardo@netscout.com \
    --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).