From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-wr0-f170.google.com (mail-wr0-f170.google.com
 [209.85.128.170]) by dpdk.org (Postfix) with ESMTP id 33AD336E
 for <dev@dpdk.org>; Tue, 28 Mar 2017 11:56:56 +0200 (CEST)
Received: by mail-wr0-f170.google.com with SMTP id w43so82558762wrb.0
 for <dev@dpdk.org>; Tue, 28 Mar 2017 02:56:56 -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=5+5rze694HIxxwrIBtf40EhgAg/gZ+xY77Niqf8sfWk=;
 b=2QG4tieJPNE3Ipa6hA6Rmj9FnDGq3+unY1I8JjmXmVXdjpCjFa7hiZzg8z01NcDkeh
 GU5D65X7WumY90DMp5e1hezz2MRczBfvGvB6Lz2kkm/J//dQN9H58NPITPxv+Vl2jHsp
 xUBWUOIcvkfWUrRAPQRizprMSdWXpjbVR9RpnqF5aQH4VWmVfeAEDYdPiTMliXO2oMBW
 TVEhG+WlhM/A+ta0un9GWDSUCcT0QhgsacG9T1MDQHwd/LuWMWyeWPxdBeWaQPY5kyiA
 MwTgKoS9c27Vol+rvpBf7RM+H5RlzVk6BX8xUd6DEGN8EHV0OynTTMCQh59nUG3K53By
 wB8w==
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=5+5rze694HIxxwrIBtf40EhgAg/gZ+xY77Niqf8sfWk=;
 b=nat488zCYLS+h198C8xsgP/2w2UJVuRmK94LUZxK9ZQrrOHsN5iicGT2vYDuG85eT4
 cO9PGuW4KSrIb9QqZDFs4u9DHs6PFESCCsiMeiAJmbmQsZGIKQkD2KM8pSyu5E8tk9eM
 x8PIJ3iBuNwKMW4kBwsmz+z45I+hkqbwpVUD0+0djn0P+GLsbHSE9SuPLRHFX9scUQ6R
 230ZRFXJgdf9bK0kAd3cw16FyPPHQs0bDY3xCGZA6eTzE39Tw1ryLq7rQQCU6AN+nYGn
 wcjtUTug07AFVPNHJ7siFbLxCmpiTga9is3eAkGlft7K4A0APSVC5LAW6X8fz6q85dsg
 w2hQ==
X-Gm-Message-State: AFeK/H1To1WG5o4Zc4P4QtBwOqtdwSgDKKQbKC5k9gI3/qn0JmfP0AK5/F/GEedpEnvopulG
X-Received: by 10.223.169.241 with SMTP id b104mr9589697wrd.88.1490695015192; 
 Tue, 28 Mar 2017 02:56:55 -0700 (PDT)
Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184])
 by smtp.gmail.com with ESMTPSA id h65sm4157291wrh.32.2017.03.28.02.56.54
 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Tue, 28 Mar 2017 02:56:54 -0700 (PDT)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: dev@dpdk.org, "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
 "jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>
Date: Tue, 28 Mar 2017 11:56:53 +0200
Message-ID: <1783560.U3ricBZEab@xps13>
User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; )
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891265277FF26@IRSMSX108.ger.corp.intel.com>
References: <2544195.RoHNEuVALo@xps13>
 <3EB4FA525960D640B5BDFFD6A3D891265277FF26@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 <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Mar 2017 09:56:56 -0000

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?

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?