From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 870B22C08 for ; Tue, 5 Apr 2016 16:04:18 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga103.jf.intel.com with ESMTP; 05 Apr 2016 07:03:42 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,444,1455004800"; d="scan'208";a="948467709" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by orsmga002.jf.intel.com with ESMTP; 05 Apr 2016 07:03:42 -0700 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.35]) by IRSMSX102.ger.corp.intel.com ([169.254.2.19]) with mapi id 14.03.0248.002; Tue, 5 Apr 2016 15:03:40 +0100 From: "Ananyev, Konstantin" To: "Doherty, Declan" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] Change new libraries to have dpdk_ prefix instead of rte_ Thread-Index: AQHRjz+7jEMIOWhhIEmMNvxdhVrNqJ97Yogw Date: Tue, 5 Apr 2016 14:03:39 +0000 Message-ID: <2601191342CEEE43887BDE71AB97725836B2E5A6@irsmsx105.ger.corp.intel.com> References: <1828032.Xk8haRDBUM@xps13> <5703BDB3.3010501@intel.com> In-Reply-To: <5703BDB3.3010501@intel.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNzExNjg2YWQtZjJhMy00OTM0LWIxZjktNGZlY2I5MDI0OWNlIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6InhFQ2s4T1U2bGVEOTZFdjl4eXhaMDdOMDdlWlwvTkd0aUczdUVZc0N2ZWdnPSJ9 x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Change new libraries to have dpdk_ prefix instead of rte_ 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: Tue, 05 Apr 2016 14:04:19 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Declan Doherty > Sent: Tuesday, April 05, 2016 2:29 PM > To: dev@dpdk.org > Subject: [dpdk-dev] Change new libraries to have dpdk_ prefix instead of = rte_ >=20 > I'd like people opinion of Thomas proposal to have all new libraries use > a dpdk_ prefix instead of rte_*. Although I agree that dpdk_ would > probably make sense, I don't like the ascetics of inconsistent prefixes > on dpdk libraries. Any comments? I suppose it is a bit strange to have rte_ prefix for one set of libraries, and dpdk_ prefix for others. If we'd decide to change the prefix, then my vote would be to do that for all dpdk libraries at once. =20 BTW, why do we need to change it at all? 'rte_' is probably not the best one, but at least it is well known/used. Konstantin=20 >=20 >=20 >=20 >=20 > 2016-04-05 09:48, Trahe, Fiona: > > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > > > 2016-04-05 08:53, Fiona Trahe: > > > > The cryptodev API was introduced in the DPDK 2.2 release. > > > > Since then it has > > > > - been reviewed and iterated for the DPDK 16.04 release > > > > - had extensive use by the l2fwd-crypto app, > > > > the ipsec-secgw example app, > > > > the test app. > > > > We believe it is now stable and the EXPERIMENTAL label should be re= moved. > > > > > > Are you sure sure? :) > > > It means you will try hard to not change the API anymore or you'll ne= ed a > > > deprecation notice strongly agreed (outside of your team). > > > > We're sure sure :) >=20 > I think we could change the namespace before making this API stable. > What about using a dpdk_ prefix instead of rte_ ? > (and some macros have CRYPTODEV or CDEV prefixes) >=20