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 5A461A0547; Fri, 12 Feb 2021 20:09:39 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 907A122A22B; Fri, 12 Feb 2021 20:09:38 +0100 (CET) Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182]) by mails.dpdk.org (Postfix) with ESMTP id EC3FD227F63 for ; Fri, 12 Feb 2021 20:09:36 +0100 (CET) Received: by linux.microsoft.com (Postfix, from userid 1086) id 203C720B6C40; Fri, 12 Feb 2021 11:09:36 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 203C720B6C40 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1613156976; bh=uSUHFuwWrN80NknQGafSZyx+OCgLS+l9S0P78UOlU4c=; h=Date:From:To:Cc:Subject:From; b=bpjCDicO97PBqZjH0sXKwQVQ5iAb4oUKlxIGQWUZs1jvESof0+cUCN0Bi/vx6XjDv Qk1me0qGx8dX+l5MkugbJKmqZQzy/BYzeXgyHfJazZL7HPnN0yyj19BOwtE/AyUyI+ GERetVlBnmk6I9W0W7rLz8SRNRsU4faUOxEy28c0= Date: Fri, 12 Feb 2021 11:09:36 -0800 From: Tyler Retzlaff To: dev@dpdk.org Cc: thomas@monjalon.net Message-ID: <20210212190936.GA2579@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: [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" Hi, 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. 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. Thank you