From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [dpdk-users] If shared libraries are used vdev doesn't work anymore Date: Mon, 31 Jul 2017 22:23:50 +0200 Message-ID: <2197043.BsW04uu1lT@xps> References: <9fb283ed-223d-713e-4722-21278f4cfd6e@ng4t.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: users@dpdk.org, dev@dpdk.org To: Dirk-Holger Lenz , gaetan.rivet@6wind.com Return-path: In-Reply-To: <9fb283ed-223d-713e-4722-21278f4cfd6e@ng4t.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 31/07/2017 16:58, Dirk-Holger Lenz: > If dpdk is built with 'CONFIG_RTE_BUILD_SHARED_LIB=y' then > using the vdev feature (args: e.g. -c 3 -n 4 --vdev="crypto_openssl") > the rte_eal_init() returns 'ERROR: failed to parse device "crypto_openssl"'. > It looks to me that rte_eal_devargs_add() calling rte_eal_devargs_parse() > is trying to check the device name before the shared libraries are read > and the internal data arrays are setup. Yes, you're right: eal_parse_args() is called before eal_plugins_init(). The fix is not small: we should split the args parsing to parse the device arguments after loading shared libraries. It is a release blocker.