From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id AE2A3A046B for ; Tue, 23 Jul 2019 09:59:11 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 54E9B1BFB7; Tue, 23 Jul 2019 09:59:10 +0200 (CEST) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by dpdk.org (Postfix) with ESMTP id 5FE621BFB7 for ; Tue, 23 Jul 2019 09:59:09 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 508925A3; Tue, 23 Jul 2019 03:59:08 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 23 Jul 2019 03:59:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=ndbnEajf10pndB1NdqhhTtr6NzQX3bBfK5N2JdpY2UQ=; b=EizzjCVDZTQG umj/ybhRJiDxSifEf55lLWym/KlXteQJmeA3YU4tq5jODndCa5wkHRrjbUpr9uCm rOqO2HgXrWE9XCqHgeYtZd/58nNmE8W/IAaKCOMDxQB+qgrmDOXHhz9B+Cc2myFi Q5AFu5X2h5H0HA7zrv/KnxVamj5dVRM= 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=ndbnEajf10pndB1NdqhhTtr6NzQX3bBfK5N2JdpY2 UQ=; b=jrTnE7VdawWeFgTMHGXcnHdx5V8ZOxTOAMCwGTbJUgyKOkJ9eqL+NFcn1 UzITcofJ/Vdjg3bOxZMMmhsOJxzfJN7B9m/zl364NOqGP9QUeUAXamRY27hpdFMP Ec3X+gkmMFDKiRi2dvqBnTxEnvETu8ASG3kYdXIKNC9t09N9CS8ZYpw2EOnyPvXg U6v+3xv+gwq4TJDxlK/oJ+CbaX8ZnsOHmJUTlFUDhQar42Dtq9NudYHqL4WyoD7c xSB6SvD0UaGiINL3TrZJlF65LVuU0G4IAzcs6UXMlBC/4F6LVE2qrD4pAJhjAJL3 otF297Qrw1+gf5/xcTkkbOmCYW11g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrjeejgdegiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id F34A8380085; Tue, 23 Jul 2019 03:59:06 -0400 (EDT) From: Thomas Monjalon To: Stephen Hemminger Cc: Bruce Richardson , dev@dpdk.org Date: Tue, 23 Jul 2019 09:59:04 +0200 Message-ID: <7229382.2RzrNnEHBx@xps> In-Reply-To: <20190722113437.3c509e0b@xps13> References: <20190715234136.3526-1-stephen@networkplumber.org> <4987111.cxvgFvst8F@xps> <20190722113437.3c509e0b@xps13> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] pci: fix missing pci bus with shared library build X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 22/07/2019 20:34, Stephen Hemminger: > On Mon, 22 Jul 2019 19:31:08 +0200 > Thomas Monjalon wrote: > > > 22/07/2019 19:13, Stephen Hemminger: > > > Thomas Monjalon wrote: > > > > Are the constructors run on dlopen of the bus driver? > > > > > > Yes, constructors are run on dlopen. > > > But application should not have to ask DPDK to dlopen the bus devices. > > > > > > The core principle is that dynamic build of DPDK should act the same as old > > > statically linked DPDK. Otherwise, the user experience is even worse, and all > > > the example documentation is wrong. > > > > OK, this is where I wanted to bring the discussion. > > You are arguing against a design which is in DPDK from some early days. > > So this is an interesting discussion to have. > > Do we want to change the "plugin model" we have? > > Or do we want to simply drop this model (dlopen calls) > > and replace it with strong dynamic linking? > > I argue that examples should work the same with dynamic linking. > This used to work before the break out of the bus model, so it is a bug. The PCI support was part of EAL, yes, but the device drivers were plugins and already required the -d option. > For distributions, this also matters. Linking with -ldpdk which is a linker > script should work. There is no longer this linker script with meson.