From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 020692C74 for ; Tue, 28 Mar 2017 11:43:02 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intel.com; i=@intel.com; q=dns/txt; s=intel; t=1490694183; x=1522230183; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=QepxDvEsQgBg5QsfT6tvrAILZSwyZnaG5TomMb2pVhg=; b=WbbzU1znekWbIzUwkE6459TiGsXKECol74dOu/Fx5E718XworrRB83k7 C+K6llJCenV7oc+pGRf2qYjEOk1tLQ==; Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Mar 2017 02:43:01 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,236,1486454400"; d="scan'208";a="1147842450" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by fmsmga002.fm.intel.com with ESMTP; 28 Mar 2017 02:43:00 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.239]) by IRSMSX153.ger.corp.intel.com ([163.33.192.75]) with mapi id 14.03.0319.002; Tue, 28 Mar 2017 10:41:21 +0100 From: "Dumitrescu, Cristian" To: Thomas Monjalon , "dev@dpdk.org" CC: "hemant.agrawal@nxp.com" , "jerin.jacob@caviumnetworks.com" Thread-Topic: new QoS/TM API and tree Thread-Index: AQHSp5+I10PdHhyEm0uIYgNbN/CWcqGp/XvA Date: Tue, 28 Mar 2017 09:41:20 +0000 Message-ID: <3EB4FA525960D640B5BDFFD6A3D891265277FF26@IRSMSX108.ger.corp.intel.com> References: <2544195.RoHNEuVALo@xps13> In-Reply-To: <2544195.RoHNEuVALo@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNTE5YWExNGQtOGU1ZC00NDE0LTkwNTUtNDkzZDEwMDdmZDQ3IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6ImJVZHNPMmtlc1JsREVhS1wvNFdKclFoTVNHdkkwV0xHOEZBQmV2WWRBeTlvPSJ9 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] new QoS/TM API and tree X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2017 09:43:03 -0000 Hi Thomas, > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Tuesday, March 28, 2017 9:44 AM > To: dev@dpdk.org > Cc: Dumitrescu, Cristian ; > hemant.agrawal@nxp.com; jerin.jacob@caviumnetworks.com > Subject: new QoS/TM API and tree >=20 > At the last techboard meeting, it has been accepted to create a new > git tree for the ongoing QoS work. > (see minutes http://dpdk.org/ml/archives/dev/2017-March/061009.html) >=20 > Quoting http://dpdk.org/ml/archives/dev/2017-March/060387.html > " > Can you please create a next-tree for QoS Traffic Management with the > following details: > Maintainer: Cristian > Committers: Hemant, Jerin, Cristian > " >=20 > The last detail to discuss is the name of this tree. > As it is probably going to be an important amount of work, this tree > can live indefinitely as a next- tree to be pulled before each RC1. > The suggested names were dpdk-next-qos and dpdk-next-tm. >=20 > The question is equivalent to choose a name for the new API. > Should it be rte_qos or rte_tm? Quality of Service (QoS) is a very generous concept that includes the egres= s Traffic Management features such as hierarchical scheduling, traffic shap= ing, congestion management, etc.; the QoS concept also includes the ingress= Traffic Metering and Policing. Therefore, I think the sensible approach is: API name (already debated on V2 thread: rte_scheddev, rte_tm, rte_tman, et= c): rte_tm Repository name: dpdk-next-qos or dpdk-next-tm (your choice) >=20 > Please let's think how it can evolve in future versions. Thanks, Cristian