From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50061.outbound.protection.outlook.com [40.107.5.61]) by dpdk.org (Postfix) with ESMTP id 0AF7E5587 for ; Fri, 18 Nov 2016 15:31:59 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nxp.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=y3i3pApfhvTfRX+BjUSfNe1cj8rtyo8f6X//9m/fwe8=; b=Y0t3EQ2gGRw+1o/9oWtWKFKgAWcmN2wYOjGDQlhQb36PQyOxhZLqLzXvpip7ArCNmOiZdSMJx0Zn6ETaCV63Nzu1TR3XLe4eK9uZomxV9OQn9TdtrYhiw5NJ4uFZbyhSbyfYemGyngmLazpQ8ABubtiK5ovBKBBxVcoZc/oXHa8= Received: from DB5PR04MB1605.eurprd04.prod.outlook.com (10.164.38.147) by DB5PR04MB1606.eurprd04.prod.outlook.com (10.164.38.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.734.8; Fri, 18 Nov 2016 14:31:58 +0000 Received: from DB5PR04MB1605.eurprd04.prod.outlook.com ([10.164.38.147]) by DB5PR04MB1605.eurprd04.prod.outlook.com ([10.164.38.147]) with mapi id 15.01.0734.007; Fri, 18 Nov 2016 14:31:58 +0000 From: Hemant Agrawal To: Thomas Monjalon CC: "dev@dpdk.org" Thread-Topic: Clarification for - SoC specific driver based common sub component placing Thread-Index: AdJBmLbhgTB4qmUzSR6rQCTFai2AhwACE0gAAAAtTQAAAahGYA== Date: Fri, 18 Nov 2016 14:31:57 +0000 Message-ID: References: <7765421.y4BZ5iUgMg@xps13> <13846356.5jcoesaunv@xps13> In-Reply-To: <13846356.5jcoesaunv@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=hemant.agrawal@nxp.com; x-originating-ip: [182.69.143.219] x-microsoft-exchange-diagnostics: 1; DB5PR04MB1606; 7:pzidL4G2tMWm0yvy2RYo9m027eCc//VcBYF5orYcrmi7EiZAckFGtRDj6aBcPDLsp7cnSYPRVD+nW4C1dLDcwGcI9z72ZC5a0qKeQMkwMh5Wo4tNk8BR5zGMndPQzD48eFmuLK4nlXxpfV9DgwV/CuTIj2QyK+wm/5rtZBbb9gqSlCqzxJhzSI4GcWzumUM3CvCCFcIQeSO0FYR2yo4dT2yLK4Py07jAGfykUNmRMImWVoyE/k/pRnH04i3CXyXswFoNSvh1+mu2PUQIKl1CcpzsZlFk79WBlUKfohkI9ouT1jn4Kx7J7dJmSisXaccjprXJi6LlKmkmNpdkV6Vl2+jzK4kE5sj4JyDlrB+aTpg= x-ms-office365-filtering-correlation-id: 7c5bb636-b1b3-4f18-4fbb-08d40fbfa6f3 x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:DB5PR04MB1606; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(185117386973197); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6045074)(6040281)(6060326)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(6061324)(6046074)(6041223); SRVR:DB5PR04MB1606; BCL:0; PCL:0; RULEID:; SRVR:DB5PR04MB1606; x-forefront-prvs: 01304918F3 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(377424004)(199003)(377454003)(13464003)(189002)(3660700001)(3280700002)(86362001)(76576001)(5660300001)(54356999)(50986999)(76176999)(6116002)(102836003)(3846002)(7696004)(31430400001)(101416001)(8936002)(87936001)(110136003)(9686002)(68736007)(81166006)(106356001)(6916009)(81156014)(2950100002)(105586002)(189998001)(92566002)(229853002)(2906002)(4326007)(97736004)(305945005)(7736002)(7846002)(122556002)(8676002)(2900100001)(66066001)(4001150100001)(77096005)(6506003)(38730400001)(33656002)(74316002); DIR:OUT; SFP:1101; SCL:1; SRVR:DB5PR04MB1606; H:DB5PR04MB1605.eurprd04.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: nxp.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: nxp.com X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Nov 2016 14:31:57.8474 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 686ea1d3-bc2b-4c6f-a92c-d99c5c301635 X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR04MB1606 Subject: Re: [dpdk-dev] Clarification for - SoC specific driver based common sub component placing X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2016 14:32:00 -0000 > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Friday, November 18, 2016 7:13 PM > To: Hemant Agrawal > Cc: dev@dpdk.org > Subject: Re: Clarification for - SoC specific driver based common sub com= ponent > placing >=20 > 2016-11-18 14:38, Thomas Monjalon: > > 2016-11-18 12:44, Hemant Agrawal: > > > We like to introduce NXP's DPAA (Data Path Acceleration Architecture = Gen2) > Poll mode drivers into the DPDK. > > > > > > We need some clarification w.r.t the right placing of some dependent > components, which can be common across drivers. E.g. We have hardware > queue and buffer manager driver. This will be used by both network driver= and > crypto driver. But it is specific to NXP platform only. > > > > > > What is the right place for such common hardware specific components = in > DPDK? > > > 1. Add a new generic Soc library structure. e.g. librte_soc/nxp/. Fo= r each > soc configuration only the required components will be compiled-in. > > > 2. Create a drivers/soc/nxp/dpaa2 structure to keep common driver li= bs. > And link the network and crypto drivers to it. > > > 3. Add it to main network driver and make the crypto driver dependen= t > on it. > > > > Your question is more generic than SoC context. > > You just want to share some code between drivers, right? > > What about building a library located in drivers/common/nxp/ ? >=20 > I'm a bit reluctant to have company name in file hierarchy, as it not som= ething > stable. And especially for NXP/Qualcomm... >=20 > In this case would it be better to name the directory drivers/common/dpaa= 2/ ? [Hemant] Sounds good.=20 Thanks!=20