In DPDK1.7, PMDs are loaded by __constructor__ functions.
As there is no direct reference to each PMD driver structures, linker may
not link the PMD library.
You should use -Wl,--whole-archive and -Wl,--no-whole-archive for linking
DPDK applications.
See http://dpdk.org/browse/dpdk/tree/mk/rte.app.
This does resolve the problem.
Thank you so much.
From: Sanford, Robert [rsanf...@akamai.com]
Sent: Tuesday, September 23, 2014 2:50 PM
To: Wang, Shawn; dev at dpdk.org
Subject: Re: [dpdk-dev] Can not init NIC after merge to DPDK 1.7 problem
We ran into
Hi:
We are using our own Makefile in building dpdk program. Recently we are working
on upgrading from DPDK 1.3 to DPDK 1.7. I found the rte_ixgbe_pmd_init has been
replaced by PMD_REGISTER_DRIVER. So I delete rte_ixgbe_pmd_init calls. But
after that, our dpdk program could not correctly find th
We ran into a similar problem when migrating to 1.7.
Here are the subtle flags, in dpdk/mk/rte.app.mk, that we needed:
LDLIBS += --whole-archive
...
LDLIBS += --no-whole-archive
This apparently tells the linker to pull in whole archive(s), even if it
thinks that we don't n
On Tue, Sep 23, 2014 at 06:53:57PM +, Wang, Shawn wrote:
> Hi:
>
> We are using our own Makefile in building dpdk program. Recently we are
> working on upgrading from DPDK 1.3 to DPDK 1.7. I found the
> rte_ixgbe_pmd_init has been replaced by PMD_REGISTER_DRIVER. So I delete
> rte_ixgbe_pmd
On Tue, Sep 23, 2014 at 06:53:57PM +, Wang, Shawn wrote:
> Can someone share some light on what is magic of the dpdk Makefile to
> correctly register the NIC type?
I had the same problem as a guy who began using it before the auto-reg,
stopped a while, and began again after.
You have to pas
6 matches
Mail list logo
