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 DEA19915D; Tue, 1 Aug 2017 11:32:58 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 3654B208EF; Tue, 1 Aug 2017 05:32:58 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 01 Aug 2017 05:32:58 -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=N1XAir8t08vTmKE ie8WK/3uzojxaWndZGOXnzWU4DD8=; b=KtQEcyVFxO7QI6FZNW9Ilu10kfMfcFG w/L4g9HHt8lOrmD5mON8jTOyXva64lOuSDDJZo0izrYm27QNdhd3ZfyFz4NceUUT sO34HzWAo7xJRqDQXC28tleLt6yVHVNG1RHD++hqPjyKn9e/sEcFTFxw954JH30k 6h/W6Etcmufk= 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=N1XAir8t08vTmKEie8WK/3uzojxaWndZGOXnzWU4DD8=; b=lQdt54IG JA7iOSrIksn5MzP9guBcW+70TMrzqG7hi6GsC/0IAoKSnV1X2jxp0XNRc0muvM1W 7oiq9weqglgeOm0Csb3jwd2mJ3+lb4AIE+MoUIljUOzXdJ4COjPHjPpYMzcQRNbZ 4WMDjmgbaZ7iLAUk8YgBv7uRfKeLO0stIz/ezhcXqkOLNYh2/LdMiIzA1C3mDALq lMZJ1S1Kk+gdXaTeeM5l8hzIXsRJz3ttiHpuq1lJkMZ7TgF+zM9rppupbT8+2G70 JZ51x+/XOS3WijGE0db9r8wA0t4Qply8X6JyiFZ/A8PHHVhcsMPvoDnfmzXPatNu XKHpzpzXYEJh/w== X-ME-Sender: X-Sasl-enc: X4TgX9kuzMej+ncPbvhEl2CkrqNlrQNbtF7KYBSOPvB2 1501579977 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id C2D977E65E; Tue, 1 Aug 2017 05:32:57 -0400 (EDT) From: Thomas Monjalon To: =?ISO-8859-1?Q?Ga=EBtan?= Rivet Cc: Dirk-Holger Lenz , users@dpdk.org, dev@dpdk.org Date: Tue, 01 Aug 2017 11:32:56 +0200 Message-ID: <3107053.nrimOLvoz2@xps> In-Reply-To: <20170801081759.GO11154@bidouze.vm.6wind.com> References: <9fb283ed-223d-713e-4722-21278f4cfd6e@ng4t.com> <2197043.BsW04uu1lT@xps> <20170801081759.GO11154@bidouze.vm.6wind.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" 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: Tue, 01 Aug 2017 09:32:59 -0000 01/08/2017 10:17, Ga=EBtan Rivet: > Hi, >=20 > On Mon, Jul 31, 2017 at 10:23:50PM +0200, Thomas Monjalon wrote: > > 31/07/2017 16:58, Dirk-Holger Lenz: > > > If dpdk is built with 'CONFIG_RTE_BUILD_SHARED_LIB=3Dy' then > > > using the vdev feature (args: e.g. -c 3 -n 4 --vdev=3D"crypto_openssl= ") > > > the rte_eal_init() returns 'ERROR: failed to parse device "crypto_ope= nssl"'. > > > It looks to me that rte_eal_devargs_add() calling rte_eal_devargs_par= se() > > > is trying to check the device name before the shared libraries are re= ad > > > and the internal data arrays are setup. > >=20 > > 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. > >=20 > > It is a release blocker. >=20 > I saw that yesterday, tried to investigate a bit. > I have currently an issue when launching testpmd when > BUILD_SHARED_LIB=3Dy. Mbufs fail to be allocated. I was not able to find > the root cause for this. Have you loaded the mempool driver? > Anyway, I guess there are two possible solutions: >=20 > - Delayed device validation > - Earlier plugins init >=20 > Thomas you seem to propose the first one, I agree that it will probably > be a little involved to implement but I guess it's feasible in time. > However, I don't yet understand why the second one is not possible from > the get-go. It makes sense in any case that the system should be > stabilized as soon as possible - i.e. that underlying subsystems such as > plugins and capabilities are loaded first to expose a stable set of > capabilities to any subsequent initializations. The problem is that the plugins initialization depends on tailqs, log and memory initialization. > So, I will lack time to investigate the issue with testpmd and shared > libs. If anyone has any idea, I will gladly hear it. In the meantime, I > will test those two solutions, see what would be feasible, and try to > propose one shortly. Thank you