diff mbox series

maintainers: set git tree for packet framework and QoS

Message ID 20200114100559.19794-1-david.marchand@redhat.com (mailing list archive)
State Superseded, archived
Headers show
Series maintainers: set git tree for packet framework and QoS | expand

Checks

Context Check Description
ci/travis-robot success Travis build: passed
ci/iol-intel-Performance success Performance Testing PASS
ci/Intel-compilation success Compilation OK
ci/iol-nxp-Performance success Performance Testing PASS
ci/iol-mellanox-Performance success Performance Testing PASS
ci/iol-testing success Testing PASS
ci/checkpatch warning coding style issues

Commit Message

David Marchand Jan. 14, 2020, 10:05 a.m. UTC
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
 MAINTAINERS | 2 ++
 1 file changed, 2 insertions(+)

Comments

Thomas Monjalon Jan. 14, 2020, 10:23 a.m. UTC | #1
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.
About ethdev TM and MTR, I am not sure what is the right thing to do.
David Marchand Jan. 14, 2020, 10:27 a.m. UTC | #2
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.
Dumitrescu, Cristian Jan. 14, 2020, 10:34 a.m. UTC | #3
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Tuesday, January 14, 2020 10:27 AM
> To: Thomas Monjalon <thomas@monjalon.net>
> Cc: dev <dev@dpdk.org>; Dumitrescu, Cristian
> <cristian.dumitrescu@intel.com>; Singh, Jasvinder
> <jasvinder.singh@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>
> Subject: Re: [PATCH] maintainers: set git tree for packet framework and QoS
> 
> 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.
> 

Yes, librte_meter should also go to the QoS tree.

> 
> > 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.
> 

Yes, these APIs are ethdev API, although QoS related.

> 
> --
> David Marchand
Thomas Monjalon Jan. 14, 2020, 10:36 a.m. UTC | #4
14/01/2020 11:27, David Marchand:
> On Tue, Jan 14, 2020 at 11:23 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> > 14/01/2020 11:05, David Marchand:
> > 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.

Yes this is my question:
Is it fine merging QoS related patches on ethdev, drivers and testpmd
in dpdk-next-net, or do we want them to be managed separately in dpdk-next-qos?
There is not much activity here, so I am just anticipating a heavier activity.
David Marchand Jan. 14, 2020, 10:46 a.m. UTC | #5
On Tue, Jan 14, 2020 at 11:36 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 14/01/2020 11:27, David Marchand:
> > On Tue, Jan 14, 2020 at 11:23 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> > > 14/01/2020 11:05, David Marchand:
> > > 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.
>
> Yes this is my question:
> Is it fine merging QoS related patches on ethdev, drivers and testpmd
> in dpdk-next-net, or do we want them to be managed separately in dpdk-next-qos?
> There is not much activity here, so I am just anticipating a heavier activity.

If we move those files under the qos subtree, it will be impossible
(?) to identify QoS only changes on those drivers, so we will end with
the patches going to master.
diff mbox series

Patch

diff --git a/MAINTAINERS b/MAINTAINERS
index b0cd0440ef..c3c263a51a 100644
--- 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
@@ -1275,6 +1276,7 @@  F: doc/guides/tools/pdump.rst
 Packet Framework
 ----------------
 M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
+T: git://dpdk.org/next/dpdk-next-pipeline
 F: lib/librte_pipeline/
 F: lib/librte_port/
 F: lib/librte_table/