From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f176.google.com (mail-wr0-f176.google.com [209.85.128.176]) by dpdk.org (Postfix) with ESMTP id C818ED075 for ; Tue, 28 Mar 2017 12:15:42 +0200 (CEST) Received: by mail-wr0-f176.google.com with SMTP id w43so83276030wrb.0 for ; Tue, 28 Mar 2017 03:15:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=v3yEu+S7UthyhmuC+608xCihTriQT3S/2qWZo8bAmDI=; b=z7xLC8DvTmN/zeQNMiQIkBRzj5Alki/r/u0tsa7kXsI/U0ss8ZmrCJPl1vrRa168ck xnK7fSpXYrvA2f56RLovanurKtU6TdyVG8pO1w0NntxtghmSsmEKzDeOoZwHPtQRfDV+ 4K1Mgy9z8lJF61vEG5Nn3sZXdEtSGOtConA03wAgQtYNkToHy+G/bgBkkyTSdzJwX6zl dYiYD5gHP2nwtAddHAlJq1QpO1rP7PL5h06dB4C/Sbz6pU9xfC52gcY7irLcVxTtA9BX 7xP3qpdmK1GnX/KsIS0Kt7Ek9vKyzZ1FSJGGMShv33Retco4NFz/pVAMO5zzsWr7Od2V HjkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=v3yEu+S7UthyhmuC+608xCihTriQT3S/2qWZo8bAmDI=; b=eVDBdjbbI+GfiS46w87Y8rivZI5fXCMyWlgKdQvoXar/5kdd7bm7vPi12xkAkJYjrL 22zfjs7fgaGVZ79+3mK1/A333nFdTq9TN9XWn/So4IWCi0RcuA5JIOPp7LwjN8EE+Lxi Wd4bviqOrYVa2W9pAh2LYxaqSPFKu8deKpuMWeYJLQZHwiH2DPVF69OJPvTwijilIkAz 0VWWp+qCG3QLPSPv9W7b7fkdIpp0BD7F5rHkOIpBGhCKYQ7AF3mbA6+eZhsVXT6cxJ1G 0ghn2qfw+Gqih4ifwIbfmevlBduWi7gvbTWKKHLZBPdZ0Xh/7d4Uryn2shn+C4ZMfk/Y nl0g== X-Gm-Message-State: AFeK/H17NLApQTf11xfnyHcFOI52HSYGftFIrS6xrtgLaX81lWckLaXiRV5taRJuWI2ABGb4 X-Received: by 10.28.86.68 with SMTP id k65mr13733913wmb.112.1490696141198; Tue, 28 Mar 2017 03:15:41 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id b91sm4249703wrd.29.2017.03.28.03.15.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Mar 2017 03:15:40 -0700 (PDT) From: Thomas Monjalon To: techboard@dpdk.org Cc: "Dumitrescu, Cristian" , dev@dpdk.org, "hemant.agrawal@nxp.com" , "jerin.jacob@caviumnetworks.com" Date: Tue, 28 Mar 2017 12:15:39 +0200 Message-ID: <2146492.CbsodXuhb0@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891265277FFDC@IRSMSX108.ger.corp.intel.com> References: <2544195.RoHNEuVALo@xps13> <1783560.U3ricBZEab@xps13> <3EB4FA525960D640B5BDFFD6A3D891265277FFDC@IRSMSX108.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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:15:42 -0000 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, traffic 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 be > > 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 repo (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 libs. Can we have an agreement by most of the techboard members please?