From: Justin Tallon <justin.tallon@softwareradiosystems.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] using dpdk as a shared library
Date: Mon, 22 Mar 2021 22:18:07 +0100 [thread overview]
Message-ID: <CA+uMv7fN2i1h6YgtYoZJSazGJ5jTNVTYmTMfy9z8b-CdgOBbSA@mail.gmail.com> (raw)
In-Reply-To: <20201221153250.0979639b@hermes.local>
Hey Stephen,
Thanks for your help previously, I am again having issues with passing
shared libraries of dpdk.
I am getting the following error
EAL: RTE_LPM tailq is already registered
PANIC in tailqinitfn_rte_lpm_tailq():
Cannot initialize tailq: RTE_LPM
Only when using dpdk as a shared library, I have tried many things but
there is very little online about this, any suggestions would
be appreciated!
Thanks,
Justin
____
Justin Tallon Ph.D.
Software Radio Systems (SRS)
http://www.softwareradiosystems.com
+353-86-067-0753 | justin.tallon@softwareradiosystems.com
On Tue, Dec 22, 2020 at 12:33 AM Stephen Hemminger <
stephen@networkplumber.org> wrote:
> On Tue, 22 Dec 2020 00:20:51 +0100
> Justin Tallon <justin.tallon@softwareradiosystems.com> wrote:
>
> > Hey Stephen,
> >
> > Thanks for the response, I have passed the directory of the dpdk library
> as
> > you said with the -d flag.
> >
> > However, when I did this, I get the following error.
> >
> > libdpdk.so: invalid ELF header
> >
> > any help with this would be appreciated.
> >
> > Regards,
> > Justin
> >
>
> You need to pass the individual pmd library name.
> libdpdk.so is a linker script, not a real shared library.
> It disappeared in later versions.
>
prev parent reply other threads:[~2021-03-22 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 22:38 Justin Tallon
2020-12-19 19:27 ` Stephen Hemminger
2020-12-21 23:20 ` Justin Tallon
2020-12-21 23:32 ` Stephen Hemminger
2021-03-22 21:18 ` Justin Tallon [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=CA+uMv7fN2i1h6YgtYoZJSazGJ5jTNVTYmTMfy9z8b-CdgOBbSA@mail.gmail.com \
--to=justin.tallon@softwareradiosystems.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).