maintainers: set git tree for packet framework and QoS
PATCH 1/1 maintainers: set git tree for packet framework and QoS
--- MAINTAINERS | 2 ++ 1 file changed, 2 insertions(+)
MAINTAINERS +2 -0
@@ -1256,6 +1256,7 @@ F: doc/guides/sample_app_ug/packet_ordering.rst Hierarchical scheduler M: Cristian Dumitrescu <[email protected]> M: Jasvinder Singh <[email protected]> +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 <[email protected]> +T: git://dpdk.org/next/dpdk-next-pipeline F: lib/librte_pipeline/ F: lib/librte_port/ F: lib/librte_table/
Signature · 1 line
2.23.0
14/01/2020 11:05, David Marchand:
MAINTAINERS F: doc/guides/sample_app_ug/packet_ordering.rst · line 1262
Quoted 10 lines
MAINTAINERS +1
-0@@ -1256,6 +1256,7 @@ F: doc/guides/sample_app_ug/packet_ordering.rst Hierarchical scheduler M: Cristian Dumitrescu <[email protected]> M: Jasvinder Singh <[email protected]> +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.
Quoted 14 lines · Thomas Monjalon
14/01/2020 11:05, David Marchand:
MAINTAINERS F: doc/guides/sample_app_ug/packet_ordering.rst · line 1262
Quoted 10 lines
MAINTAINERS +1
-0@@ -1256,6 +1256,7 @@ F: doc/guides/sample_app_ug/packet_ordering.rst Hierarchical scheduler M: Cristian Dumitrescu <[email protected]> M: Jasvinder Singh <[email protected]> +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_meteris also candidate to QoS tree.
Argh, thought I had double checked... ok will fix.
Quoted 1 line
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.
Signature · 1 line
David Marchand
Quoted 27 lines
-----Original Message-----
From: David Marchand <[email protected]>
Sent: Tuesday, January 14, 2020 10:27 AM
To: Thomas Monjalon <[email protected]>
Cc: dev <[email protected]>; Dumitrescu, Cristian <[email protected]>; Singh, Jasvinder <[email protected]>; Yigit, Ferruh <[email protected]>
Subject: Re: [PATCH] maintainers: set git tree for packet framework and QoSQuoted 5 lines · Thomas Monjalon
14/01/2020 11:05, David Marchand:
MAINTAINERS F:
Quoted 3 lines
MAINTAINERS +0
-0@@ -1256,6 +1256,7 @@ F:
doc/guides/sample_app_ug/packet_ordering.rstQuoted 8 lines
Quoted 7 lines
MAINTAINERS +1
-0Hierarchical scheduler M: Cristian Dumitrescu <[email protected]> M: Jasvinder Singh <[email protected]> +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
Quoted 4 lines
Quoted 1 line
librte_meteris also candidate to QoS tree.Argh, thought I had double checked... ok will fix.
Yes, librte_meter should also go to the QoS tree.
Quoted 5 lines
Quoted 2 lines
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.
Quoted 3 lines
--
David Marchand
14/01/2020 11:27, David Marchand:
Quoted 5 lines · Thomas Monjalon
Quoted 2 lines
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.
Quoted 6 lines · Thomas Monjalon
14/01/2020 11:27, David Marchand:
Quoted 4 lines · Thomas Monjalon
Quoted 2 lines
14/01/2020 11:05, David Marchand:
About ethdev TM and MTR, I am not sure what is the right thing to do.
Quoted 6 lines
Quoted 1 line
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.
Signature · 1 line
David Marchand
PATCH v2 1/1 maintainers: set git tree for packet framework and QoS
In reply to David MarchandMark librte_meter and librte_sched as being handled in the dpdk-next-qos subtree.
The packet framework bits go through dpdk-next-pipeline.
--- MAINTAINERS | 3 +++ 1 file changed, 3 insertions(+)
MAINTAINERS +3 -0
@@ -1256,6 +1256,7 @@ F: doc/guides/sample_app_ug/packet_ordering.rst Hierarchical scheduler M: Cristian Dumitrescu <[email protected]> M: Jasvinder Singh <[email protected]> +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 <[email protected]> +T: git://dpdk.org/next/dpdk-next-pipeline F: lib/librte_pipeline/ F: lib/librte_port/ F: lib/librte_table/
@@ -1341,6 +1343,7 @@ F: app/test/test_fib* Traffic metering M: Cristian Dumitrescu <[email protected]> +T: git://dpdk.org/next/dpdk-next-qos F: lib/librte_meter/ F: doc/guides/sample_app_ug/qos_scheduler.rst F: app/test/test_meter.c
Signature · 1 line
2.23.0
Thomas Monjalon
Applied14/01/2020 14:09, David Marchand:
Quoted 5 lines
Mark
librte_meterandlibrte_schedas being handled in the dpdk-next-qos subtree.
The packet framework bits go through dpdk-next-pipeline.Signed-off-by David Marchand <[email protected]>
Applied, thanks