From: David Marchand <david.marchand@redhat.com>
To: Satish Patel <satish.txt@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: intel X550T dpdk support issue
Date: Tue, 5 Oct 2021 08:54:42 +0200 [thread overview]
Message-ID: <CAJFAV8wRApaT_+v5rbY-QHT1+dcRzB+aV4NDLD--r4Gd+72oww@mail.gmail.com> (raw)
In-Reply-To: <CAPgF-fouTfevTaEVOBxqAqcwJRtLrFEra8sBfK2XBKZwW6+AJQ@mail.gmail.com>
On Mon, Oct 4, 2021 at 11:20 PM Satish Patel <satish.txt@gmail.com> wrote:
>
> Is this my issue ?
No.
For this specific trace below, you are probably trying to attach a
secondary process to a primary process (which was OVS iiuc) which does
not have the same enabled DPDK libraries/drivers.
Having the same dpdk components (from the same version) in both
binaries is the only way for multiprocess to work: I'd recommend
linking both your binaries against a built once and for all set of
dpdk libraries.
Besides, please note that the OVS does not support multiprocess.
Issues had been reported in the past (like pdump secondary process
crashing OVS).
There is work atm in OVS that will make multiprocess disabled.
>
> # dpdk-proc-info
> EAL: Detected 48 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_4651_a967f74152a
> EAL: Selected IOVA mode 'VA'
> EAL: Probing VFIO support...
> EAL: VFIO support initialized
> EAL: Cannot initialize tailq: RTE_EVENT_RING
> Tailq 0: qname:<RTE_RING>, tqh_first:(nil), tqh_last:0x100004488
> Tailq 1: qname:<RTE_HASH>, tqh_first:(nil), tqh_last:0x1000044b8
> Tailq 2: qname:<RTE_FBK_HASH>, tqh_first:(nil), tqh_last:0x1000044e8
> Tailq 3: qname:<RTE_MEMPOOL>, tqh_first:(nil), tqh_last:0x100004518
> Tailq 4: qname:<RTE_MBUF_DYNFIELD>, tqh_first:(nil), tqh_last:0x100004548
> Tailq 5: qname:<RTE_MBUF_DYNFLAG>, tqh_first:(nil), tqh_last:0x100004578
> Tailq 6: qname:<UIO_RESOURCE_LIST>, tqh_first:(nil), tqh_last:0x1000045a8
> Tailq 7: qname:<VFIO_RESOURCE_LIST>, tqh_first:(nil), tqh_last:0x1000045d8
> Tailq 8: qname:<>, tqh_first:(nil), tqh_last:(nil)
> Tailq 9: qname:<>, tqh_first:(nil), tqh_last:(nil)
> Tailq 10: qname:<>, tqh_first:(nil), tqh_last:(nil)
> Tailq 11: qname:<>, tqh_first:(nil), tqh_last:(nil)
--
David Marchand
next prev parent reply other threads:[~2021-10-05 6:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 18:52 Satish Patel
2021-10-04 21:20 ` Satish Patel
2021-10-05 6:54 ` David Marchand [this message]
2021-10-05 6:58 ` David Marchand
2021-10-21 13:59 ` Satish Patel
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=CAJFAV8wRApaT_+v5rbY-QHT1+dcRzB+aV4NDLD--r4Gd+72oww@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=satish.txt@gmail.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).