Hi Thomas,
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monja...@6wind.com]
> Sent: Tuesday, March 28, 2017 9:44 AM
> To: dev@dpdk.org
> Cc: Dumitrescu, Cristian <cristian.dumitre...@intel.com>;
> hemant.agra...@nxp.com; jerin.ja...@caviumnetworks.com
> Subject: new QoS/TM API and tree
>
> 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?
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.
Thanks,
Cristian
