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 9C557A056A; Wed, 10 Mar 2021 21:53:06 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1BB8022A4D2; Wed, 10 Mar 2021 21:53:06 +0100 (CET) Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) by mails.dpdk.org (Postfix) with ESMTP id 9908F40F35 for ; Wed, 10 Mar 2021 21:53:04 +0100 (CET) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 119911106; Wed, 10 Mar 2021 15:53:02 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 10 Mar 2021 15:53:02 -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= nLEqi9a7+IYPl+txAqycFSGr7Awdr1UGvvBN0JYJ8KQ=; b=ffjjVtQJ+Lx/+RpL tdF+SGG67pw7/XEKqaXTl0WGdBR/BxITv9ueLkqWXK7L5xWmlaBzHB7FqiafGJyZ 6AGep075vaWmW4bSHTXBpGehlNDkcGhQLRMviA+CH8rVxUTRCWzo/dMasvvcr0Cm 5dSR50gOUhr1WQpgxNncVPW4cEJimwcgKTRjvfQk7qGppm5sWh3/6+oUrVIGk46P WD0gEQ4ZUdFIIUVRSPyc/LxnuJCdcWJgfTcHdHRs94UkHIiaXCtJ4tZPb8REQzYC 3cbDkrj90/3SMIun1fg+pgmaOy3zIdTDwsx4Fs/wudWIFZsxXVpZLk2w9U/ZRmUQ AwHu6w== 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=nLEqi9a7+IYPl+txAqycFSGr7Awdr1UGvvBN0JYJ8 KQ=; b=hANWdDNinA6TkJ5OOgVQHlixXRvH81JcVPhpsOdcQ6M+aB/KS182DZOv0 ILiyNgo8LWmmT1ygFo15HYjtO+8WVR45ahsDTQT05jp4i0eRy/R/Rxc0hQDjC50i hrtXEsaodcyPDvGsyC0ExX5cLTYchycXbrkZuWWlaE8GY9MDK1065r44P6aQTiOT 5eXlCn7rx/86LRvaHX/gTo0GVaklkxNAQI2gmkY246rNFH2h4uw+Q3mcNbPQ/5v5 nz8ODMYmfY9VtXCBJMUMjxdB/wQAMsdtqsySlel341xDmW1B0KqUeUnvtOk27OB6 7Sq9Hv5tBC1inkk2dut/P+pFBXnTQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledruddukedgudegvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkfgjfhgggfgtsehtuf ertddttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghs sehmohhnjhgrlhhonhdrnhgvtheqnecuggftrfgrthhtvghrnhepudeggfdvfeduffdtfe eglefghfeukefgfffhueejtdetuedtjeeuieeivdffgeehnecukfhppeejjedrudefgedr vddtfedrudekgeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght 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 9B8D124005E; Wed, 10 Mar 2021 15:53:00 -0500 (EST) From: Thomas Monjalon To: Tyler Retzlaff Cc: dev@dpdk.org, bruce.richardson@intel.com, olivier.matz@6wind.com Date: Wed, 10 Mar 2021 21:52:58 +0100 Message-ID: <4724511.8By67KtOdl@thomas> In-Reply-To: <20210212190936.GA2579@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> References: <20210212190936.GA2579@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] officially support building driver plugins externally X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 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" 12/02/2021 20:09, Tyler Retzlaff: > Recently installation of driver headers and export of functions was pulled back from being public to private (commit df96fd0d73955bdc7ca3909e772ff2ad903249c6). From a discussion with Thomas Monjalon we understand that it was not the design intent to ever have these headers exposed publicly, but it was allowing us to maintain the drivers we do implement outside of the normal dpdk tree. > > We would like to propose that building driver plugins external to the dpdk source tree be officially supported / restored and it is is our understanding there there are asks from other DPDK consumers for the same. We understand the main concern is that it might incorrectly convey that the API/ABI of the driver interface is stable or promised to be compatible when no such promise exists. Yes we must have a clean API export for application. The driver interface should not be exported by default. > Can the broader community help us with an acceptable solution to building the drivers out of the tree? Aside from installing the needed headers what other mechanical things can we do to achieve this? We are happy to do the work/submit the required patches as necessary. What about a meson option to export the driver interface files? Should it be exported in the same include directory as API files? Should it be accessible with a pkg-config file?