From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 4141C2C74 for ; Tue, 28 Mar 2017 12:09:14 +0200 (CEST) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga105.jf.intel.com with ESMTP; 28 Mar 2017 03:09:13 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,236,1486454400"; d="scan'208";a="80121669" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by orsmga005.jf.intel.com with ESMTP; 28 Mar 2017 03:09:11 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.239]) by IRSMSX104.ger.corp.intel.com ([163.33.3.159]) with mapi id 14.03.0319.002; Tue, 28 Mar 2017 11:09:10 +0100 From: "Dumitrescu, Cristian" To: Thomas Monjalon CC: "dev@dpdk.org" , "hemant.agrawal@nxp.com" , "jerin.jacob@caviumnetworks.com" Thread-Topic: new QoS/TM API and tree Thread-Index: AQHSp5+I10PdHhyEm0uIYgNbN/CWcqGp/XvA///1w4CAABE2MA== Date: Tue, 28 Mar 2017 10:09:09 +0000 Message-ID: <3EB4FA525960D640B5BDFFD6A3D891265277FFDC@IRSMSX108.ger.corp.intel.com> References: <2544195.RoHNEuVALo@xps13> <3EB4FA525960D640B5BDFFD6A3D891265277FF26@IRSMSX108.ger.corp.intel.com> <1783560.U3ricBZEab@xps13> In-Reply-To: <1783560.U3ricBZEab@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYzNiZjNmNzUtMTFiNi00MDQ1LWIxNDYtZWJhMDQ4NWJmNGYzIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IkZzbnVNTUpOOXA2SXJ3VGk4TXV5TjNTVzRKNVdKNFl5cCtXREp1d3Z5WTQ9In0= 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 10:09:14 -0000 > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Tuesday, March 28, 2017 10:57 AM > To: Dumitrescu, Cristian > Cc: dev@dpdk.org; hemant.agrawal@nxp.com; > jerin.jacob@caviumnetworks.com > Subject: Re: new QoS/TM API and tree >=20 > 2017-03-28 09:41, Dumitrescu, Cristian: > > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > > > 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. > > > > > > 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 e= gress > 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, etc): rte_tm > > Repository name: dpdk-next-qos or dpdk-next-tm (your choice) > > > > > Please let's think how it can evolve in future versions. >=20 > The question is: > Are we sure that every features included in this "next" repo will be > only about Traffic Management? What we are 100% sure of is the API name of rte_tm, as this API is exclusiv= ely targeting traffic management. I agree with you that dpdk-next-qos would be a better name for the repo (in= stead of dpdk-next-tm), in case we want to add other QoS functionality to e= thdev over time, such as traffic metering and policing. Of course, this is = subject to community interest and Tech Board approval. >=20 > Detailed in two questions: > - Are we sure the QoS API of ethdev will be only about Traffic Management= ? > - Do we want to manage other QoS code areas in this "next" repo?