All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Cc: cristian.dumitrescu@intel.com, hemant.agrawal@nxp.com,
	jerin.jacob@caviumnetworks.com
Subject: new QoS/TM API and tree
Date: Tue, 28 Mar 2017 10:44:20 +0200	[thread overview]
Message-ID: <2544195.RoHNEuVALo@xps13> (raw)

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.

             reply	other threads:[~2017-03-28  8:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28  8:44 Thomas Monjalon [this message]
2017-03-28  9:41 ` new QoS/TM API and tree Dumitrescu, Cristian
2017-03-28  9:56   ` Thomas Monjalon
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=2544195.RoHNEuVALo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.