From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 171B5A0550 for ; Wed, 10 Feb 2021 10:25:11 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 03BD21606C6; Wed, 10 Feb 2021 10:25:11 +0100 (CET) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by mails.dpdk.org (Postfix) with ESMTP id 11C5440142; Wed, 10 Feb 2021 10:25:08 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 8F190C2E; Wed, 10 Feb 2021 04:25:04 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 10 Feb 2021 04:25:05 -0500 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=fm3; bh= KFjhl7GeJ5pzQfER1B1DkAQCzYJjOqxJptY6dRL+o2c=; b=I+WIXbmZdxCzIwLV n08mqE/mYWIuORMQSivn1K89g/Ctsq+pdURnOBj8SY/M4wwT8p6FtOfwjo0Urm/A YwljWPQ0un75T7TvS9dRODi5cUeRr32xOYbLJ/S/nQ5bXYp+Ka21lXF1i5qv+0NB 7Ad+xcO3QSjXFO38l0BhwfedVDmRLfMcJGVM8IOX2SC+SvZSxTslDEiMMBKGpF4o k899boBwc6R3e5TZ0ZaEMjS+Ikg7yO3NnJGAGjX/8pb0NvlCGKrP9RjLwE1qpPNb gvfrjlN+Cs2XMQU2FAo5hx9LQT0nbpS3fKmbf4Jvtf2N9MyrFIi2L8Lm1p0AMW1B Uiuu/Q== 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=fm2; bh=KFjhl7GeJ5pzQfER1B1DkAQCzYJjOqxJptY6dRL+o 2c=; b=oOV8oe3KHCmgDVBb8zydbkJk6d2mwWHO+E4oPhZXbukC0gppmc5Vepwn9 xl2YSt4ElK56CmQ7UsHM0C8gfaDnQJqOW8gGPAkpAP9Q5r6nNEPobtcBxB80XC0b x++G6IzePY+yTWsFM/Npd6FQpucEptf7jmTQkbf4xuZyi4uTZiYB4OrU10ztsREt L79bENgPbTZITA8lyjB7SQ+zTxKx99VpEybkKsznPYMWwrul4fwKFjhNU1HxhzSr Nukp76SYVNg9dhU8HpSbDbTD9GTJFtsGj0FDODlcF6b3JSVyxRSICzMxk+axSXpy HgafZ2KGh99sRkj5FPAWX0h1zdp0w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrheejgddtfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdejueei iedvffegheenucfkphepjeejrddufeegrddvtdefrddukeegnecuvehluhhsthgvrhfuih iivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho nhdrnhgvth 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 A0351108005C; Wed, 10 Feb 2021 04:25:02 -0500 (EST) From: Thomas Monjalon To: "Richardson, Bruce" Cc: "dev@dpdk.org" , "tredaelli@redhat.com" , "stable@dpdk.org" , Maxime Coquelin , David Marchand , "bluca@debian.org" , "Pai G, Sunil" Date: Wed, 10 Feb 2021 10:25:00 +0100 Message-ID: <1852982.GJMhToD9Xh@thomas> In-Reply-To: References: <20210208163319.507567-1-bruce.richardson@intel.com> <20210209124951.GE1208@bricha3-MOBL.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] eal: fix detection of static or shared DPDK builds X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" 09/02/2021 21:10, Pai G, Sunil: > Hi Bruce, > > Thanks for the fix. > I do see the issue mentioned when using DPDK shared libs with OVS and this patch fixes it. > > However, I saw the issue only for system installed DPDK but not for directory installed DPDK. > > > > I saw this issue with OVS, where I was getting weird failures about ports not > > being bound (in case of physical ports) or not being created (in case of virtio > > ports), when using a shared build. Since it's potentially serious, I'd appreciate > > if someone can reproduce the issue and verify the fix so we can consider it > > for 21.02 inclusion. > > > > To demonstrate this with regular DPDK, do a usual build of DPDK and then do > > "ninja install" to install system-wide. Then build an example app, e.g. > > l2fwd, using "make" from the examples/l2fwd directory. Running the > > example normally, e.g. ./build/l2fwd -c F00, leads to no drivers being loaded > > or ports being found. Adding "-d /path/to/drivers" e.g. > > "/usr/local/lib/x86_64-linux-gnu/dpdk/pmds-21.1" on my system works as > > expected. This shows the driver loading is not correct. > > > > After applying this patch and re-running "ninja install", l2fwd should run the > > same with and without the "-d" flag. > > > > /Bruce > > Tested-by: Sunil Pai G Applied, thanks