From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev <dev@dpdk.org>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] maintainers: set git tree for packet framework and QoS
Date: Tue, 14 Jan 2020 11:27:03 +0100 [thread overview]
Message-ID: <CAJFAV8w8L=K-Ji+xvciDODje2bW1GNihXwnwUZo4Q-=uyEaqVg@mail.gmail.com> (raw)
In-Reply-To: <1926662.K71DO8KEF6@xps>
On Tue, Jan 14, 2020 at 11:23 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 14/01/2020 11:05, David Marchand:
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -1256,6 +1256,7 @@ F: doc/guides/sample_app_ug/packet_ordering.rst
> > Hierarchical scheduler
> > M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> > M: Jasvinder Singh <jasvinder.singh@intel.com>
> > +T: git://dpdk.org/next/dpdk-next-qos
> > F: lib/librte_sched/
> > F: doc/guides/prog_guide/qos_framework.rst
> > F: app/test/test_red.c
>
> librte_meter is also candidate to QoS tree.
Argh, thought I had double checked... ok will fix.
> About ethdev TM and MTR, I am not sure what is the right thing to do.
The drivers using those apis are in dpdk-next-net.
--
David Marchand
next prev parent reply other threads:[~2020-01-14 10:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 10:05 David Marchand
2020-01-14 10:23 ` Thomas Monjalon
2020-01-14 10:27 ` David Marchand [this message]
2020-01-14 10:34 ` Dumitrescu, Cristian
2020-01-14 10:36 ` Thomas Monjalon
2020-01-14 10:46 ` David Marchand
2020-01-14 13:09 ` [dpdk-dev] [PATCH v2] " David Marchand
2020-01-22 21:45 ` 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='CAJFAV8w8L=K-Ji+xvciDODje2bW1GNihXwnwUZo4Q-=uyEaqVg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jasvinder.singh@intel.com \
--cc=thomas@monjalon.net \
/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).