From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: new QoS/TM API and tree
Date: Tue, 28 Mar 2017 10:44:20 +0200
Message-ID: <2544195.RoHNEuVALo@xps13>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: cristian.dumitrescu@intel.com, hemant.agrawal@nxp.com,
 jerin.jacob@caviumnetworks.com
To: dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wr0-f173.google.com (mail-wr0-f173.google.com
 [209.85.128.173]) by dpdk.org (Postfix) with ESMTP id 8B612CFBA
 for <dev@dpdk.org>; Tue, 28 Mar 2017 10:44:22 +0200 (CEST)
Received: by mail-wr0-f173.google.com with SMTP id w43so79829712wrb.0
 for <dev@dpdk.org>; Tue, 28 Mar 2017 01:44:22 -0700 (PDT)
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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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)

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
"

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?

Please let's think how it can evolve in future versions.