From: Bruce Richardson <bruce.richardson@intel.com>
To: "Shubhachint, Chaitanya" <Chaitanya.Shubhachint@netscout.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK Shared lib: No Ethernet ports
Date: Mon, 10 Sep 2018 11:46:51 +0100 [thread overview]
Message-ID: <20180910104651.GA24376@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <DM5PR0101MB29543A2D5F54762DCC627A1887000@DM5PR0101MB2954.prod.exchangelabs.com>
On Fri, Sep 07, 2018 at 05:11:21PM +0000, Shubhachint, Chaitanya wrote:
> Thank you for your reply Bruce.
> Still having issues with shared-lib DPDK. I tried both options and get two distinct issues.
> I tried running the l2fwd example with e1000 driver and get little farther. This time it does find the devices but there is an error with MBUF
>
> root:build$./l2fwd -d /home/sp2/dpdk-18.08/x86_64-native-linuxapp-gcc/lib/librte_pmd_e1000.so
> EAL: Detected 6 lcore(s)
> EAL: Detected 1 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: No free hugepages reported in hugepages-1048576kB
> EAL: Probing VFIO support...
> EAL: PCI device 0000:00:19.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:1502 net_e1000_em
> EAL: PCI device 0000:06:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:06:00.1 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:06:00.2 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:06:00.3 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:08:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10d3 net_e1000_em
> MAC updating enabled
> MBUF: error setting mempool handler
> EAL: Error - exiting with code: 1
> Cause: Cannot init mbuf pool
>
> 2nd Option of setting CONFIG_RTE_EAL_PMD_PATH option is ideal, but I run into issue with as well. I am configuring and installing the DPDK with CONFIG_RTE_EAL_PMD_PATH set as
> CONFIG_RTE_EAL_PMD_PATH=$(HOME)/dpdk-18.08/x86_64-native-linuxapp-gcc/lib
>
> I this case I get following error when I run l2fwd
>
> root:build$./l2fwd
> EAL: Detected 6 lcore(s)
> EAL: Detected 1 NUMA nodes
> EAL: /home/sp2/dpdk-18.08/x86_64-native-linuxapp-gcc/lib/libdpdk.so: invalid ELF header
> EAL: FATAL: Cannot init plugins
>
> EAL: Cannot init plugins
>
> EAL: Error - exiting with code: 1
> Cause: Invalid EAL arguments
>
To use CONFIG_RTE_EAL_PMD_PATH, you really need to have the drivers all in
a separate directory, without any additional libs present. Other non-PMD
libraries will cause the error above when they are loaded.
/Bruce
prev parent reply other threads:[~2018-09-10 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 14:18 Shubhachint, Chaitanya
2018-09-07 14:22 ` Richardson, Bruce
2018-09-07 17:11 ` Shubhachint, Chaitanya
2018-09-10 10:46 ` Bruce Richardson [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=20180910104651.GA24376@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=Chaitanya.Shubhachint@netscout.com \
--cc=dev@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).