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>
Subject: Re: [dpdk-dev] new QoS/TM API and tree
Date: Tue, 28 Mar 2017 11:56:53 +0200 [thread overview]
Message-ID: <1783560.U3ricBZEab@xps13> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891265277FF26@IRSMSX108.ger.corp.intel.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?
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?
next prev parent reply other threads:[~2017-03-28 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 8:44 Thomas Monjalon
2017-03-28 9:41 ` Dumitrescu, Cristian
2017-03-28 9:56 ` Thomas Monjalon [this message]
2017-03-28 10:09 ` Dumitrescu, Cristian
2017-03-28 10:15 ` Thomas Monjalon
2017-03-28 10:20 ` Jerin Jacob
2017-03-28 10:24 ` Dumitrescu, Cristian
2017-03-28 12:47 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1783560.U3ricBZEab@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).