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 E32B5CF90; Tue, 28 Mar 2017 12:24:49 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intel.com; i=@intel.com; q=dns/txt; s=intel; t=1490696690; x=1522232690; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=sBerPf7bmu07Z1ZbY0StyCWfgjHodVeCj/lQxSprT3E=; b=EkBnyU4z+Yn/QnJrSlt7Mdq3HPu87YzQUhmnW8PhtpxMIoviFJ47Fjyu aRcw46wmt6VqieJ+cl3lgTsgxbpHCw==; Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Mar 2017 03:24:45 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,236,1486454400"; d="scan'208";a="1112892696" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by orsmga001.jf.intel.com with ESMTP; 28 Mar 2017 03:24:44 -0700 Received: from irsmsx111.ger.corp.intel.com (10.108.20.4) by IRSMSX153.ger.corp.intel.com (163.33.192.75) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 28 Mar 2017 11:24:43 +0100 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.239]) by irsmsx111.ger.corp.intel.com ([169.254.2.58]) with mapi id 14.03.0319.002; Tue, 28 Mar 2017 11:24:43 +0100 From: "Dumitrescu, Cristian" To: Jerin Jacob , Thomas Monjalon CC: "techboard@dpdk.org" , "dev@dpdk.org" , "hemant.agrawal@nxp.com" Thread-Topic: new QoS/TM API and tree Thread-Index: AQHSp5+I10PdHhyEm0uIYgNbN/CWcqGp/XvA///1w4CAABE2MP//9AiAgAABbACAABE/EA== Date: Tue, 28 Mar 2017 10:24:43 +0000 Message-ID: <3EB4FA525960D640B5BDFFD6A3D8912652780068@IRSMSX108.ger.corp.intel.com> References: <2544195.RoHNEuVALo@xps13> <1783560.U3ricBZEab@xps13> <3EB4FA525960D640B5BDFFD6A3D891265277FFDC@IRSMSX108.ger.corp.intel.com> <2146492.CbsodXuhb0@xps13> <20170328102043.25ccxngsghemijji@localhost.localdomain> In-Reply-To: <20170328102043.25ccxngsghemijji@localhost.localdomain> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZWE4MDQwYjItZDZlMC00ZWFhLTg3NzYtZjM5ODYwNmM4NDJjIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IjkrbndmbHcrdVNlXC9HV2tKZCtOWW5tRVwvODNmajZjODVQQVpEbXJZeUNoTT0ifQ== 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:24:50 -0000 > -----Original Message----- > From: Jerin Jacob [mailto:jerin.jacob@caviumnetworks.com] > Sent: Tuesday, March 28, 2017 11:21 AM > To: Thomas Monjalon > Cc: techboard@dpdk.org; Dumitrescu, Cristian > ; dev@dpdk.org; > hemant.agrawal@nxp.com > Subject: Re: new QoS/TM API and tree >=20 > On Tue, Mar 28, 2017 at 12:15:39PM +0200, Thomas Monjalon wrote: > > 2017-03-28 10:09, Dumitrescu, Cristian: > > > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > > > > 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 > egress > > > > Traffic Management features such as hierarchical scheduling, traffi= c > shaping, > > > > 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. > > > > > > > > The question is: > > > > Are we sure that every features included in this "next" repo will b= e > > > > only about Traffic Management? > > > > > > What we are 100% sure of is the API name of rte_tm, as this API is > exclusively targeting traffic management. > > > > > > I agree with you that dpdk-next-qos would be a better name for the re= po > (instead of dpdk-next-tm), in case we want to add other QoS functionality= to > ethdev over time, such as traffic metering and policing. Of course, this = is > subject to community interest and Tech Board approval. > > > > > > > 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? > > > > I think it should be dpdk-next-qos and manage also the existing QoS lib= s. > > Can we have an agreement by most of the techboard members please? >=20 > IMO, If we are moving all QoS related libraries(lib/librte_meter, > lib/librte_sched and proposed tm library) to next tree then probably 'nex= t- > qos' > make sense. If the scope is limited only for proposed tm library then > next-tm make sense. >=20 Agree. Let's call the repo dpdk-next-tm and let's limit the scope to TM API= , according to the mandate approved by the Tech Board. Thomas, can we please create this tree asap without any further delay? We n= eed to start the driver development and we are currently blocked by the rep= o not being created yet. Thanks!