[dpdk-dev] driver initialization in DPDK 2.0 built into a shared library.

2015-07-21 Thread Polevoy, Igor
the log print does not help as the method still returns -1 and goes to the rte_panic. Igor From: Keunhong Lee [mailto:dlrms...@gmail.com] Sent: Tuesday, July 14, 2015 11:42 AM To: Polevoy, Igor Cc: dev at dpdk.org Subject: Re: [dpdk-dev] driver initialization in DPDK 2.0 built into a shared

[dpdk-dev] driver initialization in DPDK 2.0 built into a shared library.

2015-07-16 Thread Zoltan Kiss
On 14/07/15 19:21, Polevoy, Igor wrote: > Hi, > We are developing an application that uses DPDK PMD functionality . > We are using a linux shared library which contains the network packets > processing code and it is statically linked with all the necessary DPDK libs. > The .so is loaded by the

[dpdk-dev] driver initialization in DPDK 2.0 built into a shared library.

2015-07-15 Thread Bruce Richardson
On Tue, Jul 14, 2015 at 06:21:33PM +, Polevoy, Igor wrote: > Hi, > We are developing an application that uses DPDK PMD functionality . > We are using a linux shared library which contains the network packets > processing code and it is statically linked with all the necessary DPDK libs. > The

[dpdk-dev] driver initialization in DPDK 2.0 built into a shared library.

2015-07-15 Thread Keunhong Lee
Did you tried 'mk/rte_app.mk' to build you application? Simply including -lrte_pmd_xxx may cause problem because PMD_REGISTER_DRIVER uses 'init' attribute, which is called before the 'main' function. See the 'start-group' and 'whole-archive' linker options. Keunhong. 2015-07-15 3:21 GMT+09:00

[dpdk-dev] driver initialization in DPDK 2.0 built into a shared library.

2015-07-14 Thread Polevoy, Igor
Hi, We are developing an application that uses DPDK PMD functionality . We are using a linux shared library which contains the network packets processing code and it is statically linked with all the necessary DPDK libs. The .so is loaded by the main program. For the DPDK compilation we have