From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 26BCF7D7F; Mon, 31 Jul 2017 22:23:53 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4F55020A82; Mon, 31 Jul 2017 16:23:52 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 31 Jul 2017 16:23:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=wZLIo7GuqKZzkp9 thaWpBwE+sIolUtpoWmT3WottdtM=; b=m4JbgF2kMMOqcY33AiQiSO9H3Cwvkye SDkhWgdexUCFY1GN7TCFYDLik+7b/FnLzfNOHhfcDPqsttoifYX+eYYEJz977rCo sBkM4QVvs57P0y1Q3R3CzZo7JxTLoCTJLASyYskjyM1p6b1Gq00uPF9uWx/4KpzF yVRZXI9PEVq4= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=wZLIo7GuqKZzkp9thaWpBwE+sIolUtpoWmT3WottdtM=; b=qDCLl45/ h108CspcDG3btxecWFwNbHUteejC9TK0wwwKip+UK/NfX2uquABiY03tREmThzOX jdRiRByIm5Y/7/i26R5bUwJ2n6Jx7wG3hTC2afOZGy+BwAiZZ6VBC4gXqAD0FEFu DDBMOC4Ld1Y4IEiUNeat4OQ2V6M6rWZ+/HQvQCmKh4/ZkAuqyGtLgFyLGeGUPEAk 1mmEQyOM5T+VHowIEg5x0eBSj8hVImEWZVFCGCSbrmjfuNOVc4SDLBWufWZirjSV bahnxb6bj9pvVlhmRYyEvab0VNvoQc85Ez/oJ65HC2cX/3PiPmNhOD6uCQlMHtms 2lmJ2wY1ILz0dg== X-ME-Sender: X-Sasl-enc: WdhWHDMFXwjGPrasaoZrkgv8ipZYGvbH3IFSs1h9M3w/ 1501532631 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id DD824243A7; Mon, 31 Jul 2017 16:23:51 -0400 (EDT) From: Thomas Monjalon To: Dirk-Holger Lenz , gaetan.rivet@6wind.com Cc: users@dpdk.org, dev@dpdk.org Date: Mon, 31 Jul 2017 22:23:50 +0200 Message-ID: <2197043.BsW04uu1lT@xps> In-Reply-To: <9fb283ed-223d-713e-4722-21278f4cfd6e@ng4t.com> References: <9fb283ed-223d-713e-4722-21278f4cfd6e@ng4t.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-users] If shared libraries are used vdev doesn't work anymore X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jul 2017 20:23:53 -0000 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.