From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerin Jacob Subject: Re: Sharing Common libs between PMDs Date: Wed, 14 Mar 2018 20:25:45 +0530 Message-ID: <20180314145538.GA2482@jerin> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev@dpdk.org" To: Liron Himi Return-path: Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01on0084.outbound.protection.outlook.com [104.47.32.84]) by dpdk.org (Postfix) with ESMTP id 4BCD84C74 for ; Wed, 14 Mar 2018 15:56:02 +0100 (CET) Content-Disposition: inline In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" -----Original Message----- > Date: Wed, 14 Mar 2018 09:34:40 +0000 > From: Liron Himi > To: "dev@dpdk.org" > CC: Liron Himi > Subject: [dpdk-dev] Sharing Common libs between PMDs > > Hi, > > We have several PMDs in DPDK that are using the same underlying common libraries. > In addition, we have plans to add some new common service into DPDK that already introduces too much complexity with the way that the code is written now. > Therefore, we would like to move all our common functions calls into one shared/common folder in DPDK and we need to find proper place for this purpose. > > Can you suggest on such a place? There was an attempt to create "driver/common" but latter the common code for NXP HW device got moved to drivers/bus/dpaa/. Linux kernel has something called "driver/soc", I think, "driver/soc" may be more appropriate. Currently DPDK's driver build dependency is in the following order (bus, mempool, net, crypto, event). Other than driver/common or driver/soc, one option could be to - Move the common code to bus or mempool and - Across the drivers, include the header files through CFLAGS if the common code is in header file http://dpdk.org/browse/dpdk/tree/drivers/event/octeontx/Makefile#n13 > > Regards, > Liron > > >