From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f181.google.com (mail-pf0-f181.google.com [209.85.192.181]) by dpdk.org (Postfix) with ESMTP id 897E03B5 for ; Thu, 21 Apr 2016 17:24:27 +0200 (CEST) Received: by mail-pf0-f181.google.com with SMTP id 184so31397505pff.0 for ; Thu, 21 Apr 2016 08:24:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-transfer-encoding; bh=gCrW0xJXL1CVpyxZJ4uSIAMrllrCyy7N7PANTQPzxm4=; b=Vbw+7rr4qhcqxC2f1mLMwywiZrJ7/MTE7ouJPyvEA9KiqLvuhfysvlzY6hXUEsAY5v 5476Pe/z3xJ1ZMI47oQEkHWiH8FBdlgvi9n/fIwRBKg35y0IuSSRxAiYwBysUoBr/Ndu FcXOPqCmPB/yBXlh98DXeoEfP1jFY4kW+Rll9Z1osNH1321g1D3n2OBlthIhPOtHWaj8 jYzr9Uu4sipsK6uaC9LK3AOZpupaDoZemX1rG5fcOULAxwIwE8MhGX+wLkTMFI5qP2H5 RDPStFkgqX6XB8pAUurFbKWxkp1mhAEGvquIoOtvqyxD/3iy0FFyim0zPoDMeDgPIprI 1Mkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:message-id:date:from:reply-to:user-agent :mime-version:to:cc:subject:references:in-reply-to :content-transfer-encoding; bh=gCrW0xJXL1CVpyxZJ4uSIAMrllrCyy7N7PANTQPzxm4=; b=SkpNRnQ3+QgTStZxnDNXxIv02/HAJc+7BEyXORyx57rPx1ZLUu4Vg4Z2H+deUtOuwJ LDgOhPINQI+YsWjmZduBojDWTld50zlq17PDMcBo78R/ZAASet+JuAuPuL3sF4IDJuvF Ue95rQJznCW/AADX0o0YsujuvrushF+HUu04lsJeN5vMAUzB0EphEciRTOMmQsTtL15l sA+U6T1UkgPSPENaelLgW9xi8JWiCe7Fhfkse1+GHobJhWm+ijLg0DSw22NFmoTTdGuV hpGpHbaZjH6TZs7gQbNN8NIjJjWH/+kOCH77q4FdiD4IvNOoVINlUKF1CwgEnPgHDML3 wxfQ== X-Gm-Message-State: AOPr4FVLHNVudReQ2dGLX6lEunfrj5XdrhMuW/Gi8smgazrxxkVwfUYUUxngjFONNoK3Yw== X-Received: by 10.98.74.133 with SMTP id c5mr21173926pfj.80.1461252266920; Thu, 21 Apr 2016 08:24:26 -0700 (PDT) Received: from Pnueli.local ([2601:644:200:ade7:d107:a992:2727:403e]) by smtp.gmail.com with ESMTPSA id r191sm1953092pfr.36.2016.04.21.08.24.25 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 21 Apr 2016 08:24:26 -0700 (PDT) Sender: Aurojit Panda Message-ID: <5718F0A7.7080002@cs.berkeley.edu> Date: Thu, 21 Apr 2016 08:24:23 -0700 From: Aurojit Panda User-Agent: Postbox 4.0.8 (Macintosh/20151105) MIME-Version: 1.0 To: Thomas Monjalon CC: dev@dpdk.org, Panu Matilainen References: <57158D01.5020407@cs.berkeley.edu> <571895D9.3090700@redhat.com> <5718EB59.5010808@cs.berkeley.edu> <2358356.HZLcvC2y3R@xps13> In-Reply-To: <2358356.HZLcvC2y3R@xps13> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [dpdk-users] DPDK 16.04 link changes cause PMD drivers to not be loaded X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: apanda@cs.berkeley.edu List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 15:24:27 -0000 Thomas Monjalon wrote: > 2016-04-21 08:01, Aurojit Panda: >> Panu Matilainen wrote: > [...] >>> Again, PMDs are *plugins* that are *meant* to be loaded at runtime. >>> That allows for all sorts of flexibility especially >>> for packaging and shipping, at some extra cost in setup complexity. >> I am all for a plugin architecture, I was merely suggesting that you >> embed some path infromation at the beginning. Also please note: >> (a) This behavior changed recently. > > What changed recently? > Change 948fd64befc3726 moved DPDK from building a shared library to using LD linker scripts. >> (b) This change is entirely undocumented, which is why I was reporting >> it in the first place. >> (c) It is actually quite unintutive, because previously ensuring >> LD_LIBRARY_PATH was correct was all that was required >> to get any DPDK application to interact with ports. > > ? > Are you talking about combined library? Yes, if you build a shared combined library, PMD drivers are not automatically loaded anymore. This implies that programs do not enumerate the set of ports on the machine. (Unless CONFIG_EAL_PMD_PATH is correctly set to the absolute directory where the built DPDK will live). > >>> For your own purposes, you can of course tweak the linking settings >>> as much as you like. Look for "plugins" in mk/rte.app.mk and change >>> the shared lib condition on the line above to "y" and there you have it. >>> But that's not the way plugins are meant to be used. >> That is not a reasonable solution given that it makes it very hard to >> track future changes to DPDK without merges. >> My alternatives neither break people's abilities to use plugins, >> nor do they impact behavior. > > Please do not hesitate to send some patch to show your solution. My initial e-mail was sent because I don't entirely understand LD linker scripts (the PMD libraries are listed within the built libdpdk.so file), so the only patch I can suggest is undoing 948fd64befc3726 in which case the behavior as I describe. > Thanks Thanks Panda