From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from MIVWSMAILOUT1.mcafee.com (mivwsmailout1.mcafee.com [161.69.47.167]) by dpdk.org (Postfix) with ESMTP id 8D89011A2 for ; Tue, 14 Jul 2015 20:29:27 +0200 (CEST) Received: from MIVEXAPP1N02.corpzone.internalzone.com (unknown [10.48.48.89]) by MIVWSMAILOUT1.mcafee.com with smtp (TLS: TLSv1/SSLv3,256bits,AES256-SHA) id 476c_6d9d_5a43f088_e232_45b3_8ea9_570604a58173; Tue, 14 Jul 2015 13:29:22 -0500 Received: from MIVEXUSR1N05.corpzone.internalzone.com (10.48.48.85) by MIVEXAPP1N02.corpzone.internalzone.com (10.48.48.89) with Microsoft SMTP Server (TLS) id 15.0.995.29; Tue, 14 Jul 2015 14:21:36 -0400 Received: from MIVEXUSR1N03.corpzone.internalzone.com (10.48.48.83) by MIVEXUSR1N05.corpzone.internalzone.com (10.48.48.85) with Microsoft SMTP Server (TLS) id 15.0.995.29; Tue, 14 Jul 2015 14:21:34 -0400 Received: from MIVEXUSR1N03.corpzone.internalzone.com ([fe80::9dc6:7939:6297:c001]) by MIVEXUSR1N03.corpzone.internalzone.com ([fe80::9dc6:7939:6297:c001%24]) with mapi id 15.00.0995.032; Tue, 14 Jul 2015 14:21:34 -0400 From: "Polevoy, Igor" To: "dev@dpdk.org" Thread-Topic: driver initialization in DPDK 2.0 built into a shared library. Thread-Index: AdC+Ydef1DsQYv+URLCbsJaGArw3FA== Date: Tue, 14 Jul 2015 18:21:33 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.48.48.243] MIME-Version: 1.0 X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 15 X-NAI-Spam-Score: 0 X-NAI-Spam-Version: 2.3.0.9393 : core <5367> : inlines <3385> : streams <1471665> : uri <1985238> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] driver initialization in DPDK 2.0 built into a shared library. X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2015 18:29:28 -0000 Hi, We are developing an application that uses DPDK PMD functionality . We are using a linux shared library which contains the network packets proc= essing 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 added the -fPIC to the GCC options. While it all worked fine with DPDK 1.6 where we had the rte_pmd_init_all me= thod, in the 2.0 version the drivers registration methods (PMD_REGISTER_DRIVER) are not called when the = shared library is loaded. Although, I can go along the lines of the rte_pmd_init all and manually cal= l the driver registration, I'm concerned that DPDK has other drivers initialization calls, and I don't actually know= which are needed or could be needed and when. Do you have any advice on that? What is the best way to resolve this issue? Thank you Igor.