From: Panu Matilainen <pmatilai@redhat.com>
To: apanda@cs.berkeley.edu, users@dpdk.org
Subject: Re: [dpdk-users] DPDK 16.04 link changes cause PMD drivers to not be loaded
Date: Wed, 20 Apr 2016 11:32:36 +0300 [thread overview]
Message-ID: <57173EA4.9000208@redhat.com> (raw)
In-Reply-To: <57158D01.5020407@cs.berkeley.edu>
On 04/19/2016 04:42 AM, Aurojit Panda wrote:
> Hi
> I was trying to run testpmd from DPDK 16.04 on Linux with kernel version
> 4.4.0-1 (ld version 2.26). My machine has two
> XL710QDA2 NICs, and I built DPDK as a shared, combined library (i.e.,
> CONFIG_RTE_BUILD_SHARED_LIB=y and
> CONFIG_RTE_BUILD_COMBINE_LIBS=y in config/common_linuxapp). I found that
> the issue is due to ld not linking against all
> libraries with the new linker script (introduced in 948fd64befc3726) but
> am not sure how to fix this. As evidence for
> this being caused by this change:
>
[...]
> As you can see librte_pmd_i40e.so is missing from the list of files.
> Furthermore, using
>
> $ LD_PRELOAD="../lib/librte_pmd_i40e.so" ./testpmd -c 0x1c00 -n 4 -w
> 82:00.0 -w 82:00.1 --file-prefix "send" -- -i
> correctly enumerates the NICs.
>
> I unfortunately do not how to fix the linker script as checked in, but
> wanted to report this bug in case someone has a fix.
The PMDs are plugins which are not really supposed to be linked in but
loaded dynamically. Set CONFIG_RTE_EAL_PMD_PATH to the location of your
drivers and they'll get loaded on DPDK initialization.
- Panu -
next prev parent reply other threads:[~2016-04-20 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 1:42 Aurojit Panda
2016-04-20 8:32 ` Panu Matilainen [this message]
2016-04-20 14:26 ` Aurojit Panda
2016-04-21 8:56 ` Panu Matilainen
2016-04-21 15:01 ` Aurojit Panda
-- strict thread matches above, loose matches on Subject: below --
2016-04-19 1:38 Aurojit Panda
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=57173EA4.9000208@redhat.com \
--to=pmatilai@redhat.com \
--cc=apanda@cs.berkeley.edu \
--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).