From: Stephen Hemminger <stephen@networkplumber.org>
To: Sudharshan Krishnakumar <sudhar.ckrishna@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Issue moving to DPDK 20.11 release
Date: Wed, 26 May 2021 13:03:11 -0700 [thread overview]
Message-ID: <20210526130311.292c934a@hermes.local> (raw)
In-Reply-To: <CAEm3rUnpoX-JOV4FBNudRNoO_kQHVkR7BEWtP4PXjNSB=ZzUXw@mail.gmail.com>
On Wed, 26 May 2021 12:41:21 -0700
Sudharshan Krishnakumar <sudhar.ckrishna@gmail.com> wrote:
> Hi Stephen,
>
> Normal for dynamically linked shared libraries, linker should load the
> dependant libraries
> based on library path under-> /etc/ld.so.conf.d$ cat x86_64-linux-gnu.conf
> # Multiarch support
> /usr/local/lib/x86_64-linux-gnu
> /lib/x86_64-linux-gnu
> /usr/lib/x86_64-linux-gnu
>
> I do have the /usr/local/lib/x86* path, which is where DPDK 20.11
> shared(*.so) libraries have been installed.
> But during launch of application, application does not seem to load those
> libraries. Normally this method works.
> Is this a DPDK issue.
>
> In any case, I followed your suggestion, did ldd -v packet_ordering-shared,
> to get the dependencies, and manually passed the
> paths to the application, but there is another error now-> MBUF: error
> setting mempool handler
>
That is true for normal linked in libraries (ie what ldd shows).
The DPDK is doing explicit dlopen to load poll-mode-drivers.
I would prefer that DPDK was smarter in this area (more like the Linux kernel)
so that it could have a catalog of PCI device vendor/id table and automatically
load the PMD; but that capability is not part of the current versions.
You have to do use -d to load the right .so
next prev parent reply other threads:[~2021-05-26 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 17:27 Sudharshan Krishnakumar
2021-05-26 17:53 ` Stephen Hemminger
2021-05-26 18:10 ` Sudharshan Krishnakumar
2021-05-26 19:41 ` Sudharshan Krishnakumar
2021-05-26 20:03 ` Stephen Hemminger [this message]
2021-05-26 20:27 ` Sudharshan Krishnakumar
2021-05-26 20:43 ` Sudharshan Krishnakumar
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=20210526130311.292c934a@hermes.local \
--to=stephen@networkplumber.org \
--cc=sudhar.ckrishna@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).