doc: deprication notice to mark tm spec as experimental
PATCH 1/1 doc: deprication notice to mark tm spec as experimental
From: Nithin Dabilpuram <[email protected]>
Based on the discussion in below mail thread, it is concluded that all traffic manager API's (rte_tm.h) need to be marked experimental till few more releases to support further improvements to spec.
https://mails.dpdk.org/archives/dev/2020-April/164970.html
Adding deprication notice for the same in advance.
--- doc/guides/rel_notes/deprecation.rst | 9 +++++++++ 1 file changed, 9 insertions(+)
doc/guides/rel_notes/deprecation.rst +9 -0
@@ -118,3 +118,12 @@ Deprecation Notices Python 2 support will be completely removed in 20.11. In 20.08, explicit deprecation warnings will be displayed when running scripts with Python 2. + +* traffic manager: Based on the discussion in the thread + https://mails.dpdk.org/archives/dev/2020-April/164970.html it turns out that + all traffic manager API's in ``rte_tm.h`` were mistakenly made stable even + though the MAINTAINER's file and header file text mentions it to be still + experimental. Given that even now, both the maintainer and other contributor's + are inclined towards keeping those API's in experimental state till some more + releases in support of spec improvements, it is decided that all API's in + ``rte_tm.h`` will be marked back as experimental in v20.11 DPDK release.
Signature · 1 line
2.8.4
Quoted 23 lines · Nithin Dabilpuram
From: Nithin Dabilpuram <[email protected]>
Based on the discussion in below mail thread, it is concluded that all traffic manager API's (
rte_tm.h) need to be marked experimental till few more releases to support further improvements to spec.https://mails.dpdk.org/archives/dev/2020-April/164970.html
Adding deprication notice for the same in advance.
Signed-off-by Nithin Dabilpuram <[email protected]>--- doc/guides/rel_notes/deprecation.rst | 9 +++++++++ 1 file changed, 9 insertions(+)doc/guides/rel_notes/deprecation.rst +0
-0@@ -118,3 +118,12 @@ Deprecation Notices Python 2 support will be completely removed in 20.11. In 20.08, explicit deprecation warnings will be displayed when running
doc/guides/rel_notes/deprecation.rst Deprecation Notices · line 129
Quoted 10 lines
doc/guides/rel_notes/deprecation.rst +9
-0scripts with Python 2. + +* traffic manager: Based on the discussion in the thread + https://mails.dpdk.org/archives/dev/2020-April/164970.html it turns out that + all traffic manager API's in ``rte_tm.h`` were mistakenly made stable even + though the MAINTAINER's file and header file text mentions it to be still + experimental. Given that even now, both the maintainer and other contributor's + are inclined towards keeping those API's in experimental state till some more + releases in support of spec improvements, it is decided that all API's in + ``rte_tm.h`` will be marked back as experimental in v20.11 DPDK release.
Slightly wordy - suggest making it a small bit more concise as follows.
* traffic manager: All traffic manager API's in ``rte_tm.h`` were mistakenly made abi stable in the v19.11 release. The TM maintainer and other contributor's have agreed to keep the TM API's as experimental in expectation of additional spec improvements. Therefore, all API's in ``rte_tm.h`` will be marked back as experimental in v20.11 DPDK release. For more detail, please see `the thread
<https://mails.dpdk.org/archives/dev/2020-April/164970.html>`_.
Ray K
Quoted 42 lines · Ray Kinsella
External Email
----------------------------------------------------------------------
Quoted 23 lines · Nithin Dabilpuram
From: Nithin Dabilpuram <[email protected]>
Based on the discussion in below mail thread, it is concluded that all traffic manager API's (
rte_tm.h) need to be marked experimental till few more releases to support further improvements to spec.Adding deprication notice for the same in advance.
Signed-off-by Nithin Dabilpuram <[email protected]>--- doc/guides/rel_notes/deprecation.rst | 9 +++++++++ 1 file changed, 9 insertions(+)doc/guides/rel_notes/deprecation.rst +0
-0@@ -118,3 +118,12 @@ Deprecation Notices Python 2 support will be completely removed in 20.11. In 20.08, explicit deprecation warnings will be displayed when runningdoc/guides/rel_notes/deprecation.rst Deprecation Notices · line 129
Quoted 10 lines
doc/guides/rel_notes/deprecation.rst +9
-0scripts with Python 2. + +* traffic manager: Based on the discussion in the thread + https://urldefense.proofpoint.com/v2/url?u=https-3A__mails.dpdk.org_archives_dev_2020-2DApril_164970.html&d=DwIDaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=FZ_tPCbgFOh18zwRPO9H0yDx8VW38vuapifdDfc8SFQ&m=fMY2AL-_MFowqy_OpcWEwioupC8kxy4GNU6R3LZP_2A&s=WCnFYbXTODzmkAWYDdBurNyAJ8Hxti2qkxXNnuoBic4&e= it turns out that + all traffic manager API's in ``rte_tm.h`` were mistakenly made stable even + though the MAINTAINER's file and header file text mentions it to be still + experimental. Given that even now, both the maintainer and other contributor's + are inclined towards keeping those API's in experimental state till some more + releases in support of spec improvements, it is decided that all API's in + ``rte_tm.h`` will be marked back as experimental in v20.11 DPDK release.Slightly wordy - suggest making it a small bit more concise as follows.
Quoted 6 lines
* traffic manager: All traffic manager API's in ``rte_tm.h`` were mistakenly made
abi stable in the v19.11 release. The TM maintainer and other contributor's have
agreed to keep the TM API's as experimental in expectation of additional spec
improvements. Therefore, all API's in ``rte_tm.h`` will be marked back as
experimental in v20.11 DPDK release. For more detail, please see `the thread
<https://urldefense.proofpoint.com/v2/url?u=https-3A__mails.dpdk.org_archives_dev_2020-2DApril_164970.html&d=DwIDaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=FZ_tPCbgFOh18zwRPO9H0yDx8VW38vuapifdDfc8SFQ&m=fMY2AL-_MFowqy_OpcWEwioupC8kxy4GNU6R3LZP_2A&s=WCnFYbXTODzmkAWYDdBurNyAJ8Hxti2qkxXNnuoBic4&e= >`_.
Ack, will send v2.
Quoted 2 lines
Ray K
PATCH v2 1/1 doc: deprication notice to mark tm spec as experimental
In reply to Nithin DabilpuramFrom: Nithin Dabilpuram <[email protected]>
Based on the discussion in mail thread, it is concluded that all traffic manager API's (rte_tm.h) need to be marked experimental till few more releases to support further improvements to spec.
https://mails.dpdk.org/archives/dev/2020-April/164970.html
Adding deprication notice for the same in advance.
--- doc/guides/rel_notes/deprecation.rst | 7 +++++++ 1 file changed, 7 insertions(+)
doc/guides/rel_notes/deprecation.rst +7 -0
@@ -118,3 +118,10 @@ Deprecation Notices Python 2 support will be completely removed in 20.11. In 20.08, explicit deprecation warnings will be displayed when running scripts with Python 2. + +* traffic manager: All traffic manager API's in ``rte_tm.h`` were mistakenly made + abi stable in the v19.11 release. The TM maintainer and other contributor's have + agreed to keep the TM API's as experimental in expectation of additional spec + improvements. Therefore, all API's in ``rte_tm.h`` will be marked back as + experimental in v20.11 DPDK release. For more details, please see `the thread + <https://mails.dpdk.org/archives/dev/2020-April/164970.html>`_.
Signature · 1 line
2.8.4
Quoted 21 lines · Nithin Dabilpuram
From: Nithin Dabilpuram <[email protected]>
Based on the discussion in mail thread, it is concluded that all traffic manager API's (
rte_tm.h) need to be marked experimental till few more releases to support further improvements to spec.https://mails.dpdk.org/archives/dev/2020-April/164970.html
Adding deprication notice for the same in advance.
Signed-off-by Nithin Dabilpuram <[email protected]>--- doc/guides/rel_notes/deprecation.rst | 7 +++++++ 1 file changed, 7 insertions(+)doc/guides/rel_notes/deprecation.rst +0
-0
doc/guides/rel_notes/deprecation.rst Deprecation Notices · line 127
Quoted 10 lines
doc/guides/rel_notes/deprecation.rst +7
-0@@ -118,3 +118,10 @@ Deprecation Notices Python 2 support will be completely removed in 20.11. In 20.08, explicit deprecation warnings will be displayed when running scripts with Python 2. + +* traffic manager: All traffic manager API's in ``rte_tm.h`` were mistakenly made + abi stable in the v19.11 release. The TM maintainer and other contributor's have + agreed to keep the TM API's as experimental in expectation of additional spec + improvements. Therefore, all API's in ``rte_tm.h`` will be marked back as + experimental in v20.11 DPDK release. For more details, please see `the thread + <https://mails.dpdk.org/archives/dev/2020-April/164970.html>`_.
Quoted 51 lines
-----Original Message-----
From: Nithin Dabilpuram <[email protected]>
Sent: Tuesday, May 5, 2020 9:08 AM
To: Yigit, Ferruh <[email protected]>; Richardson, Bruce <[email protected]>; Dumitrescu, Cristian <[email protected]>; [email protected]; [email protected]; Singh, Jasvinder <[email protected]>; [email protected]; Kinsella, Ray <[email protected]>; [email protected]; [email protected]; [email protected]; Mcnamara, John <[email protected]>; Kovacevic, Marko <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; Nithin Dabilpuram <[email protected]>
Subject: [PATCH v2] doc: deprication notice to mark tm spec as experimentalFrom: Nithin Dabilpuram <[email protected]>
Based on the discussion in mail thread, it is concluded that all traffic manager API's (
rte_tm.h) need to be marked experimental till few more releases to support further improvements to spec.https://mails.dpdk.org/archives/dev/2020-April/164970.html
Adding deprication notice for the same in advance.
Signed-off-by Nithin Dabilpuram <[email protected]>--- doc/guides/rel_notes/deprecation.rst | 7 +++++++ 1 file changed, 7 insertions(+)doc/guides/rel_notes/deprecation.rst +2
-0@@ -118,3 +118,10 @@ Deprecation Notices Python 2 support will be completely removed in 20.11. In 20.08, explicit deprecation warnings will be displayed when running scripts with Python 2. + +* traffic manager: All traffic manager API's in ``rte_tm.h`` were mistakenlymade
+ abi stable in the v19.11 release. The TM maintainer and other contributor's have
+ agreed to keep the TM API's as experimental in expectation of additional specdoc/guides/rel_notes/deprecation.rst +2
-0+ improvements. Therefore, all API's in ``rte_tm.h`` will be marked back as + experimental in v20.11 DPDK release. For more details, please see `the
Quoted 4 lines
thread
+ <https://mails.dpdk.org/archives/dev/2020-April/164970.html>`_.
--
2.8.4
Jerin Jacob
Acked-byQuoted 50 lines · Cristian
Quoted 50 lines
-----Original Message-----
From: Nithin Dabilpuram <[email protected]>
Sent: Tuesday, May 5, 2020 9:08 AM
To: Yigit, Ferruh <[email protected]>; Richardson, Bruce <[email protected]>; Dumitrescu, Cristian <[email protected]>; [email protected]; [email protected]; Singh, Jasvinder <[email protected]>; [email protected]; Kinsella, Ray <[email protected]>; [email protected]; [email protected]; [email protected]; Mcnamara, John <[email protected]>; Kovacevic, Marko <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; Nithin Dabilpuram <[email protected]>
Subject: [PATCH v2] doc: deprication notice to mark tm spec as experimentalFrom: Nithin Dabilpuram <[email protected]>
Based on the discussion in mail thread, it is concluded that all traffic manager API's (
rte_tm.h) need to be marked experimental till few more releases to support further improvements to spec.https://mails.dpdk.org/archives/dev/2020-April/164970.html
Adding deprication notice for the same in advance.
Signed-off-by Nithin Dabilpuram <[email protected]>--- doc/guides/rel_notes/deprecation.rst | 7 +++++++ 1 file changed, 7 insertions(+)doc/guides/rel_notes/deprecation.rst +2
-0@@ -118,3 +118,10 @@ Deprecation Notices Python 2 support will be completely removed in 20.11. In 20.08, explicit deprecation warnings will be displayed when running scripts with Python 2. + +* traffic manager: All traffic manager API's in ``rte_tm.h`` were mistakenlymade
+ abi stable in the v19.11 release. The TM maintainer and other contributor's have
+ agreed to keep the TM API's as experimental in expectation of additional spec
Quoted 8 lines
Quoted 6 lines
doc/guides/rel_notes/deprecation.rst +2
-0+ improvements. Therefore, all API's in ``rte_tm.h`` will be marked back as + experimental in v20.11 DPDK release. For more details, please see `thethread
+ <https://mails.dpdk.org/archives/dev/2020-April/164970.html>`_.
--
2.8.4
Quoted 1 line
Hi Thomas,
Can this be merged as it was discussed and agreed long back.
--
Nithin
Quoted 72 lines · On Thu, May 21, 2020, 16:19 Jerin Jacob <[email protected]> wrote:
Quoted 18 lines · Cristian
Quoted 18 lines
-----Original Message-----
From: Nithin Dabilpuram <[email protected]>
Sent: Tuesday, May 5, 2020 9:08 AM
To: Yigit, Ferruh <[email protected]>; Richardson, Bruce <[email protected]>; Dumitrescu, Cristian <[email protected]>; [email protected]; [email protected]; Singh, Jasvinder <[email protected]>; [email protected]; Kinsella, Ray <[email protected]>; [email protected]; [email protected]; [email protected]; Mcnamara, John <[email protected]>; Kovacevic, Marko <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; Nithin Dabilpuram <[email protected]>
Subject: [PATCH v2] doc: deprication notice to mark tm spec asexperimental
Quoted 16 lines
Quoted 16 lines
From: Nithin Dabilpuram <[email protected]>
Based on the discussion in mail thread, it is concluded that all traffic manager API's (
rte_tm.h) need to be marked experimental till few more releases to support further improvements to spec.https://mails.dpdk.org/archives/dev/2020-April/164970.html
Adding deprication notice for the same in advance.
Signed-off-by Nithin Dabilpuram <[email protected]>--- doc/guides/rel_notes/deprecation.rst | 7 +++++++ 1 file changed, 7 insertions(+)Quoted 8 lines
doc/guides/rel_notes/deprecation.rst Deprecation Notices · line 119
Quoted 8 lines
doc/guides/rel_notes/deprecation.rst +0
-0@@ -118,3 +118,10 @@ Deprecation Notices Python 2 support will be completely removed in 20.11. In 20.08, explicit deprecation warnings will be displayed whenrunning
Quoted 3 lines
doc/guides/rel_notes/deprecation.rst Deprecation Notices
Quoted 3 lines
doc/guides/rel_notes/deprecation.rst +2
-0scripts with Python 2. + +* traffic manager: All traffic manager API's in ``rte_tm.h`` weremistakenly
Quoted 2 lines
Quoted 2 lines
made
+ abi stable in the v19.11 release. The TM maintainer and othercontributor's
Quoted 2 lines
Quoted 2 lines
have
+ agreed to keep the TM API's as experimental in expectation ofadditional
Quoted 2 lines
Quoted 2 lines
spec
+ improvements. Therefore, all API's in ``rte_tm.h`` will be markedback as
Quoted 1 line
Quoted 1 line
+ experimental in v20.11 DPDK release. For more details, please see
`the
Quoted 6 lines
Quoted 4 lines
thread
+ <https://mails.dpdk.org/archives/dev/2020-April/164970.html>`_.
--
2.8.4Acked-by Jerin Jacob <[email protected]>Quoted 1 line
Quoted 23 lines
Quoted 23 lines
Quoted 22 lines
From: Nithin Dabilpuram <[email protected]>
Based on the discussion in mail thread, it is concluded that all traffic manager API's (
rte_tm.h) need to be marked experimental till few more releases to support further improvements to spec.https://mails.dpdk.org/archives/dev/2020-April/164970.html
Adding deprication notice for the same in advance.
Signed-off-by Nithin Dabilpuram <[email protected]>---
+* traffic manager: All traffic manager API's in ``rte_tm.h`` were mistakenly made
+ abi stable in the v19.11 release. The TM maintainer and other contributor's have
+ agreed to keep the TM API's as experimental in expectation of additional spec(quoted diff) +2
-0+ improvements. Therefore, all API's in ``rte_tm.h`` will be marked back as + experimental in v20.11 DPDK release. For more details, please see `thethread
+ <https://mails.dpdk.org/archives/dev/2020-April/164970.html>`_.
Quoted 2 lines
Quoted 1 line
Acked-by Jerin Jacob <[email protected]>
Applied, thanks
PATCH 1/1 ethdev: mark all traffic manager API as experimental
In reply to Nithin DabilpuramThis patch marks all traffic manager API as experimental as per deprecation notice[1] and discussion[2] mentioned in following threads.
[1] https://mails.dpdk.org/archives/dev/2020-May/166221.html
[2] https://mails.dpdk.org/archives/dev/2020-April/165364.html
--- lib/librte_ethdev/rte_ethdev_version.map | 62 ++++++++++++++++---------------- lib/librte_ethdev/rte_tm.h | 33 ++++++++++++++++- 2 files changed, 64 insertions(+), 31 deletions(-)
lib/librte_ethdev/rte_ethdev_version.map +32 -30
@@ -135,36 +135,6 @@ DPDK_20.0 { rte_flow_isolate; rte_flow_query; rte_flow_validate; - rte_tm_capabilities_get; - rte_tm_get_number_of_leaf_nodes; - rte_tm_hierarchy_commit; - rte_tm_level_capabilities_get; - rte_tm_mark_ip_dscp; - rte_tm_mark_ip_ecn; - rte_tm_mark_vlan_dei; - rte_tm_node_add; - rte_tm_node_capabilities_get; - rte_tm_node_cman_update; - rte_tm_node_delete; - rte_tm_node_parent_update; - rte_tm_node_resume; - rte_tm_node_shaper_update; - rte_tm_node_shared_shaper_update; - rte_tm_node_shared_wred_context_update; - rte_tm_node_stats_read; - rte_tm_node_stats_update; - rte_tm_node_suspend; - rte_tm_node_type_get; - rte_tm_node_wfq_weight_mode_update; - rte_tm_node_wred_context_update; - rte_tm_shaper_profile_add; - rte_tm_shaper_profile_delete; - rte_tm_shared_shaper_add_update; - rte_tm_shared_shaper_delete; - rte_tm_shared_wred_context_add_update; - rte_tm_shared_wred_context_delete; - rte_tm_wred_profile_add; - rte_tm_wred_profile_delete; local: *; };
@@ -241,6 +211,38 @@ EXPERIMENTAL { __rte_ethdev_trace_rx_burst; __rte_ethdev_trace_tx_burst; rte_flow_get_aged_flows; + + # Marked as experimental in 20.11 + rte_tm_capabilities_get; + rte_tm_get_number_of_leaf_nodes; + rte_tm_hierarchy_commit; + rte_tm_level_capabilities_get; + rte_tm_mark_ip_dscp; + rte_tm_mark_ip_ecn; + rte_tm_mark_vlan_dei; + rte_tm_node_add; + rte_tm_node_capabilities_get; + rte_tm_node_cman_update; + rte_tm_node_delete; + rte_tm_node_parent_update; + rte_tm_node_resume; + rte_tm_node_shaper_update; + rte_tm_node_shared_shaper_update; + rte_tm_node_shared_wred_context_update; + rte_tm_node_stats_read; + rte_tm_node_stats_update; + rte_tm_node_suspend; + rte_tm_node_type_get; + rte_tm_node_wfq_weight_mode_update; + rte_tm_node_wred_context_update; + rte_tm_shaper_profile_add; + rte_tm_shaper_profile_delete; + rte_tm_shared_shaper_add_update; + rte_tm_shared_shaper_delete; + rte_tm_shared_wred_context_add_update; + rte_tm_shared_wred_context_delete; + rte_tm_wred_profile_add; + rte_tm_wred_profile_delete; }; INTERNAL {
lib/librte_ethdev/rte_tm.h +32 -1
@@ -16,7 +16,8 @@* traffic shaping, congestion management, packet marking, etc. * * @warning -* @b EXPERIMENTAL: this API may change without prior notice +* @b EXPERIMENTAL: +* All functions in this file may be changed or removed without prior notice. */ #include <stdint.h>
@@ -1050,6 +1051,7 @@ struct rte_tm_error {* @return * 0 on success, non-zero error code otherwise. */ +__rte_experimental int rte_tm_get_number_of_leaf_nodes(uint16_t port_id, uint32_t *n_leaf_nodes,
@@ -1074,6 +1076,7 @@ rte_tm_get_number_of_leaf_nodes(uint16_t port_id,* @return * 0 on success, non-zero error code otherwise. */ +__rte_experimental int rte_tm_node_type_get(uint16_t port_id, uint32_t node_id,
@@ -1092,6 +1095,7 @@ rte_tm_node_type_get(uint16_t port_id,* @return * 0 on success, non-zero error code otherwise. */ +__rte_experimental int rte_tm_capabilities_get(uint16_t port_id, struct rte_tm_capabilities *cap,
@@ -1112,6 +1116,7 @@ rte_tm_capabilities_get(uint16_t port_id,* @return * 0 on success, non-zero error code otherwise. */ +__rte_experimental int rte_tm_level_capabilities_get(uint16_t port_id, uint32_t level_id,
@@ -1132,6 +1137,7 @@ rte_tm_level_capabilities_get(uint16_t port_id,* @return * 0 on success, non-zero error code otherwise. */ +__rte_experimental int rte_tm_node_capabilities_get(uint16_t port_id, uint32_t node_id,
@@ -1157,6 +1163,7 @@ rte_tm_node_capabilities_get(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_n_max */ +__rte_experimental int rte_tm_wred_profile_add(uint16_t port_id, uint32_t wred_profile_id,
@@ -1180,6 +1187,7 @@ rte_tm_wred_profile_add(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_n_max */ +__rte_experimental int rte_tm_wred_profile_delete(uint16_t port_id, uint32_t wred_profile_id,
@@ -1211,6 +1219,7 @@ rte_tm_wred_profile_delete(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_shared_n_max */ +__rte_experimental int rte_tm_shared_wred_context_add_update(uint16_t port_id, uint32_t shared_wred_context_id,
@@ -1235,6 +1244,7 @@ rte_tm_shared_wred_context_add_update(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_shared_n_max */ +__rte_experimental int rte_tm_shared_wred_context_delete(uint16_t port_id, uint32_t shared_wred_context_id,
@@ -1259,6 +1269,7 @@ rte_tm_shared_wred_context_delete(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_n_max */ +__rte_experimental int rte_tm_shaper_profile_add(uint16_t port_id, uint32_t shaper_profile_id,
@@ -1282,6 +1293,7 @@ rte_tm_shaper_profile_add(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_n_max */ +__rte_experimental int rte_tm_shaper_profile_delete(uint16_t port_id, uint32_t shaper_profile_id,
@@ -1311,6 +1323,7 @@ rte_tm_shaper_profile_delete(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_shared_n_max */ +__rte_experimental int rte_tm_shared_shaper_add_update(uint16_t port_id, uint32_t shared_shaper_id,
@@ -1334,6 +1347,7 @@ rte_tm_shared_shaper_add_update(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_shared_n_max */ +__rte_experimental int rte_tm_shared_shaper_delete(uint16_t port_id, uint32_t shared_shaper_id,
@@ -1402,6 +1416,7 @@ rte_tm_shared_shaper_delete(uint16_t port_id,* @see RTE_TM_NODE_LEVEL_ID_ANY * @see struct rte_tm_capabilities */ +__rte_experimental int rte_tm_node_add(uint16_t port_id, uint32_t node_id,
@@ -1435,6 +1450,7 @@ rte_tm_node_add(uint16_t port_id,* * @see RTE_TM_UPDATE_NODE_ADD_DELETE */ +__rte_experimental int rte_tm_node_delete(uint16_t port_id, uint32_t node_id,
@@ -1459,6 +1475,7 @@ rte_tm_node_delete(uint16_t port_id,* @see rte_tm_node_resume() * @see RTE_TM_UPDATE_NODE_SUSPEND_RESUME */ +__rte_experimental int rte_tm_node_suspend(uint16_t port_id, uint32_t node_id,
@@ -1482,6 +1499,7 @@ rte_tm_node_suspend(uint16_t port_id,* @see rte_tm_node_suspend() * @see RTE_TM_UPDATE_NODE_SUSPEND_RESUME */ +__rte_experimental int rte_tm_node_resume(uint16_t port_id, uint32_t node_id,
@@ -1523,6 +1541,7 @@ rte_tm_node_resume(uint16_t port_id,* @see rte_tm_node_add() * @see rte_tm_node_delete() */ +__rte_experimental int rte_tm_hierarchy_commit(uint16_t port_id, int clear_on_fail,
@@ -1563,6 +1582,7 @@ rte_tm_hierarchy_commit(uint16_t port_id,* @see RTE_TM_UPDATE_NODE_PARENT_KEEP_LEVEL * @see RTE_TM_UPDATE_NODE_PARENT_CHANGE_LEVEL */ +__rte_experimental int rte_tm_node_parent_update(uint16_t port_id, uint32_t node_id,
@@ -1592,6 +1612,7 @@ rte_tm_node_parent_update(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_private_n_max */ +__rte_experimental int rte_tm_node_shaper_update(uint16_t port_id, uint32_t node_id,
@@ -1619,6 +1640,7 @@ rte_tm_node_shaper_update(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_shared_n_max */ +__rte_experimental int rte_tm_node_shared_shaper_update(uint16_t port_id, uint32_t node_id,
@@ -1646,6 +1668,7 @@ rte_tm_node_shared_shaper_update(uint16_t port_id,* @see enum rte_tm_stats_type * @see RTE_TM_UPDATE_NODE_STATS */ +__rte_experimental int rte_tm_node_stats_update(uint16_t port_id, uint32_t node_id,
@@ -1674,6 +1697,7 @@ rte_tm_node_stats_update(uint16_t port_id,* @see RTE_TM_UPDATE_NODE_WFQ_WEIGHT_MODE * @see RTE_TM_UPDATE_NODE_N_SP_PRIORITIES */ +__rte_experimental int rte_tm_node_wfq_weight_mode_update(uint16_t port_id, uint32_t node_id,
@@ -1697,6 +1721,7 @@ rte_tm_node_wfq_weight_mode_update(uint16_t port_id,* * @see RTE_TM_UPDATE_NODE_CMAN */ +__rte_experimental int rte_tm_node_cman_update(uint16_t port_id, uint32_t node_id,
@@ -1721,6 +1746,7 @@ rte_tm_node_cman_update(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_private_n_max */ +__rte_experimental int rte_tm_node_wred_context_update(uint16_t port_id, uint32_t node_id,
@@ -1746,6 +1772,7 @@ rte_tm_node_wred_context_update(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_shared_n_max */ +__rte_experimental int rte_tm_node_shared_wred_context_update(uint16_t port_id, uint32_t node_id,
@@ -1778,6 +1805,7 @@ rte_tm_node_shared_wred_context_update(uint16_t port_id,* * @see enum rte_tm_stats_type */ +__rte_experimental int rte_tm_node_stats_read(uint16_t port_id, uint32_t node_id,
@@ -1815,6 +1843,7 @@ rte_tm_node_stats_read(uint16_t port_id,* * @see struct rte_tm_capabilities::mark_vlan_dei_supported */ +__rte_experimental int rte_tm_mark_vlan_dei(uint16_t port_id, int mark_green,
@@ -1865,6 +1894,7 @@ rte_tm_mark_vlan_dei(uint16_t port_id,* @see struct rte_tm_capabilities::mark_ip_ecn_tcp_supported * @see struct rte_tm_capabilities::mark_ip_ecn_sctp_supported */ +__rte_experimental int rte_tm_mark_ip_ecn(uint16_t port_id, int mark_green,
@@ -1913,6 +1943,7 @@ rte_tm_mark_ip_ecn(uint16_t port_id,* * @see struct rte_tm_capabilities::mark_ip_dscp_supported */ +__rte_experimental int rte_tm_mark_ip_dscp(uint16_t port_id, int mark_green,
Signature · 1 line
2.8.4
Re: [dpdk-dev] [PATCH] ethdev: mark all traffic manager API as experimental
lib/librte_ethdev/rte_ethdev_version.map
Quoted 35 lines
-----Original Message-----
From: Nithin Dabilpuram <[email protected]>
Sent: Wednesday, September 9, 2020 6:22 PM
To: Yigit, Ferruh <[email protected]>; Richardson, Bruce <[email protected]>; Dumitrescu, Cristian <[email protected]>; [email protected]; [email protected]; Singh, Jasvinder <[email protected]>; [email protected]; Kinsella, Ray <[email protected]>; [email protected]; [email protected]; [email protected]; Ray Kinsella <[email protected]>
Cc: [email protected]; [email protected]; Nithin Dabilpuram <[email protected]>
Subject: [PATCH] ethdev: mark all traffic manager API as experimentalThis patch marks all traffic manager API as experimental as per deprecation notice[1] and discussion[2] mentioned in following threads.
[1] https://mails.dpdk.org/archives/dev/2020-May/166221.html
[2] https://mails.dpdk.org/archives/dev/2020-April/165364.htmlSigned-off-by Nithin Dabilpuram <[email protected]>--- lib/librte_ethdev/rte_ethdev_version.map | 62 ++++++++++++++++--------- ------- lib/librte_ethdev/rte_tm.h | 33 ++++++++++++++++- 2 files changed, 64 insertions(+), 31 deletions(-)lib/librte_ethdev/rte_ethdev_version.map +0
-0
Re: [dpdk-dev] [PATCH] ethdev: mark all traffic manager API as experimental
In reply to Nithin DabilpuramQuoted 3 lines · Nithin Dabilpuram
This patch marks all traffic manager API as experimental as per deprecation notice[1] and discussion[2] mentioned in following threads.
Can you please remove mentioned deprecation notice in this patch?
Quoted 5 lines
[1] https://mails.dpdk.org/archives/dev/2020-May/166221.html
[2] https://mails.dpdk.org/archives/dev/2020-April/165364.htmlSigned-off-by Nithin Dabilpuram <[email protected]>
<...>
PATCH v2 1/1 ethdev: mark all traffic manager API as experimental
In reply to Nithin DabilpuramThis patch marks all traffic manager API as experimental as per discussion mentioned in below thread.
https://mails.dpdk.org/archives/dev/2020-April/165364.html
---
v2:
- Updated commit message.
lib/librte_ethdev/rte_ethdev_version.map | 62 ++++++++++++++++---------------- lib/librte_ethdev/rte_tm.h | 33 ++++++++++++++++- 2 files changed, 64 insertions(+), 31 deletions(-)
lib/librte_ethdev/rte_ethdev_version.map +32 -30
@@ -135,36 +135,6 @@ DPDK_20.0 { rte_flow_isolate; rte_flow_query; rte_flow_validate; - rte_tm_capabilities_get; - rte_tm_get_number_of_leaf_nodes; - rte_tm_hierarchy_commit; - rte_tm_level_capabilities_get; - rte_tm_mark_ip_dscp; - rte_tm_mark_ip_ecn; - rte_tm_mark_vlan_dei; - rte_tm_node_add; - rte_tm_node_capabilities_get; - rte_tm_node_cman_update; - rte_tm_node_delete; - rte_tm_node_parent_update; - rte_tm_node_resume; - rte_tm_node_shaper_update; - rte_tm_node_shared_shaper_update; - rte_tm_node_shared_wred_context_update; - rte_tm_node_stats_read; - rte_tm_node_stats_update; - rte_tm_node_suspend; - rte_tm_node_type_get; - rte_tm_node_wfq_weight_mode_update; - rte_tm_node_wred_context_update; - rte_tm_shaper_profile_add; - rte_tm_shaper_profile_delete; - rte_tm_shared_shaper_add_update; - rte_tm_shared_shaper_delete; - rte_tm_shared_wred_context_add_update; - rte_tm_shared_wred_context_delete; - rte_tm_wred_profile_add; - rte_tm_wred_profile_delete; local: *; };
@@ -241,6 +211,38 @@ EXPERIMENTAL { __rte_ethdev_trace_rx_burst; __rte_ethdev_trace_tx_burst; rte_flow_get_aged_flows; + + # Marked as experimental in 20.11 + rte_tm_capabilities_get; + rte_tm_get_number_of_leaf_nodes; + rte_tm_hierarchy_commit; + rte_tm_level_capabilities_get; + rte_tm_mark_ip_dscp; + rte_tm_mark_ip_ecn; + rte_tm_mark_vlan_dei; + rte_tm_node_add; + rte_tm_node_capabilities_get; + rte_tm_node_cman_update; + rte_tm_node_delete; + rte_tm_node_parent_update; + rte_tm_node_resume; + rte_tm_node_shaper_update; + rte_tm_node_shared_shaper_update; + rte_tm_node_shared_wred_context_update; + rte_tm_node_stats_read; + rte_tm_node_stats_update; + rte_tm_node_suspend; + rte_tm_node_type_get; + rte_tm_node_wfq_weight_mode_update; + rte_tm_node_wred_context_update; + rte_tm_shaper_profile_add; + rte_tm_shaper_profile_delete; + rte_tm_shared_shaper_add_update; + rte_tm_shared_shaper_delete; + rte_tm_shared_wred_context_add_update; + rte_tm_shared_wred_context_delete; + rte_tm_wred_profile_add; + rte_tm_wred_profile_delete; }; INTERNAL {
lib/librte_ethdev/rte_tm.h +32 -1
@@ -16,7 +16,8 @@* traffic shaping, congestion management, packet marking, etc. * * @warning -* @b EXPERIMENTAL: this API may change without prior notice +* @b EXPERIMENTAL: +* All functions in this file may be changed or removed without prior notice. */ #include <stdint.h>
@@ -1050,6 +1051,7 @@ struct rte_tm_error {* @return * 0 on success, non-zero error code otherwise. */ +__rte_experimental int rte_tm_get_number_of_leaf_nodes(uint16_t port_id, uint32_t *n_leaf_nodes,
@@ -1074,6 +1076,7 @@ rte_tm_get_number_of_leaf_nodes(uint16_t port_id,* @return * 0 on success, non-zero error code otherwise. */ +__rte_experimental int rte_tm_node_type_get(uint16_t port_id, uint32_t node_id,
@@ -1092,6 +1095,7 @@ rte_tm_node_type_get(uint16_t port_id,* @return * 0 on success, non-zero error code otherwise. */ +__rte_experimental int rte_tm_capabilities_get(uint16_t port_id, struct rte_tm_capabilities *cap,
@@ -1112,6 +1116,7 @@ rte_tm_capabilities_get(uint16_t port_id,* @return * 0 on success, non-zero error code otherwise. */ +__rte_experimental int rte_tm_level_capabilities_get(uint16_t port_id, uint32_t level_id,
@@ -1132,6 +1137,7 @@ rte_tm_level_capabilities_get(uint16_t port_id,* @return * 0 on success, non-zero error code otherwise. */ +__rte_experimental int rte_tm_node_capabilities_get(uint16_t port_id, uint32_t node_id,
@@ -1157,6 +1163,7 @@ rte_tm_node_capabilities_get(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_n_max */ +__rte_experimental int rte_tm_wred_profile_add(uint16_t port_id, uint32_t wred_profile_id,
@@ -1180,6 +1187,7 @@ rte_tm_wred_profile_add(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_n_max */ +__rte_experimental int rte_tm_wred_profile_delete(uint16_t port_id, uint32_t wred_profile_id,
@@ -1211,6 +1219,7 @@ rte_tm_wred_profile_delete(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_shared_n_max */ +__rte_experimental int rte_tm_shared_wred_context_add_update(uint16_t port_id, uint32_t shared_wred_context_id,
@@ -1235,6 +1244,7 @@ rte_tm_shared_wred_context_add_update(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_shared_n_max */ +__rte_experimental int rte_tm_shared_wred_context_delete(uint16_t port_id, uint32_t shared_wred_context_id,
@@ -1259,6 +1269,7 @@ rte_tm_shared_wred_context_delete(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_n_max */ +__rte_experimental int rte_tm_shaper_profile_add(uint16_t port_id, uint32_t shaper_profile_id,
@@ -1282,6 +1293,7 @@ rte_tm_shaper_profile_add(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_n_max */ +__rte_experimental int rte_tm_shaper_profile_delete(uint16_t port_id, uint32_t shaper_profile_id,
@@ -1311,6 +1323,7 @@ rte_tm_shaper_profile_delete(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_shared_n_max */ +__rte_experimental int rte_tm_shared_shaper_add_update(uint16_t port_id, uint32_t shared_shaper_id,
@@ -1334,6 +1347,7 @@ rte_tm_shared_shaper_add_update(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_shared_n_max */ +__rte_experimental int rte_tm_shared_shaper_delete(uint16_t port_id, uint32_t shared_shaper_id,
@@ -1402,6 +1416,7 @@ rte_tm_shared_shaper_delete(uint16_t port_id,* @see RTE_TM_NODE_LEVEL_ID_ANY * @see struct rte_tm_capabilities */ +__rte_experimental int rte_tm_node_add(uint16_t port_id, uint32_t node_id,
@@ -1435,6 +1450,7 @@ rte_tm_node_add(uint16_t port_id,* * @see RTE_TM_UPDATE_NODE_ADD_DELETE */ +__rte_experimental int rte_tm_node_delete(uint16_t port_id, uint32_t node_id,
@@ -1459,6 +1475,7 @@ rte_tm_node_delete(uint16_t port_id,* @see rte_tm_node_resume() * @see RTE_TM_UPDATE_NODE_SUSPEND_RESUME */ +__rte_experimental int rte_tm_node_suspend(uint16_t port_id, uint32_t node_id,
@@ -1482,6 +1499,7 @@ rte_tm_node_suspend(uint16_t port_id,* @see rte_tm_node_suspend() * @see RTE_TM_UPDATE_NODE_SUSPEND_RESUME */ +__rte_experimental int rte_tm_node_resume(uint16_t port_id, uint32_t node_id,
@@ -1523,6 +1541,7 @@ rte_tm_node_resume(uint16_t port_id,* @see rte_tm_node_add() * @see rte_tm_node_delete() */ +__rte_experimental int rte_tm_hierarchy_commit(uint16_t port_id, int clear_on_fail,
@@ -1563,6 +1582,7 @@ rte_tm_hierarchy_commit(uint16_t port_id,* @see RTE_TM_UPDATE_NODE_PARENT_KEEP_LEVEL * @see RTE_TM_UPDATE_NODE_PARENT_CHANGE_LEVEL */ +__rte_experimental int rte_tm_node_parent_update(uint16_t port_id, uint32_t node_id,
@@ -1592,6 +1612,7 @@ rte_tm_node_parent_update(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_private_n_max */ +__rte_experimental int rte_tm_node_shaper_update(uint16_t port_id, uint32_t node_id,
@@ -1619,6 +1640,7 @@ rte_tm_node_shaper_update(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_shared_n_max */ +__rte_experimental int rte_tm_node_shared_shaper_update(uint16_t port_id, uint32_t node_id,
@@ -1646,6 +1668,7 @@ rte_tm_node_shared_shaper_update(uint16_t port_id,* @see enum rte_tm_stats_type * @see RTE_TM_UPDATE_NODE_STATS */ +__rte_experimental int rte_tm_node_stats_update(uint16_t port_id, uint32_t node_id,
@@ -1674,6 +1697,7 @@ rte_tm_node_stats_update(uint16_t port_id,* @see RTE_TM_UPDATE_NODE_WFQ_WEIGHT_MODE * @see RTE_TM_UPDATE_NODE_N_SP_PRIORITIES */ +__rte_experimental int rte_tm_node_wfq_weight_mode_update(uint16_t port_id, uint32_t node_id,
@@ -1697,6 +1721,7 @@ rte_tm_node_wfq_weight_mode_update(uint16_t port_id,* * @see RTE_TM_UPDATE_NODE_CMAN */ +__rte_experimental int rte_tm_node_cman_update(uint16_t port_id, uint32_t node_id,
@@ -1721,6 +1746,7 @@ rte_tm_node_cman_update(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_private_n_max */ +__rte_experimental int rte_tm_node_wred_context_update(uint16_t port_id, uint32_t node_id,
@@ -1746,6 +1772,7 @@ rte_tm_node_wred_context_update(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_shared_n_max */ +__rte_experimental int rte_tm_node_shared_wred_context_update(uint16_t port_id, uint32_t node_id,
@@ -1778,6 +1805,7 @@ rte_tm_node_shared_wred_context_update(uint16_t port_id,* * @see enum rte_tm_stats_type */ +__rte_experimental int rte_tm_node_stats_read(uint16_t port_id, uint32_t node_id,
@@ -1815,6 +1843,7 @@ rte_tm_node_stats_read(uint16_t port_id,* * @see struct rte_tm_capabilities::mark_vlan_dei_supported */ +__rte_experimental int rte_tm_mark_vlan_dei(uint16_t port_id, int mark_green,
@@ -1865,6 +1894,7 @@ rte_tm_mark_vlan_dei(uint16_t port_id,* @see struct rte_tm_capabilities::mark_ip_ecn_tcp_supported * @see struct rte_tm_capabilities::mark_ip_ecn_sctp_supported */ +__rte_experimental int rte_tm_mark_ip_ecn(uint16_t port_id, int mark_green,
@@ -1913,6 +1943,7 @@ rte_tm_mark_ip_ecn(uint16_t port_id,* * @see struct rte_tm_capabilities::mark_ip_dscp_supported */ +__rte_experimental int rte_tm_mark_ip_dscp(uint16_t port_id, int mark_green,
Signature · 1 line
2.8.4
Re: [dpdk-dev] [PATCH v2] ethdev: mark all traffic manager API as experimental
Quoted 83 lines · Nithin Dabilpuram
This patch marks all traffic manager API as experimental as per discussion mentioned in below thread.
https://mails.dpdk.org/archives/dev/2020-April/165364.html
Signed-off-by Nithin Dabilpuram <[email protected]>---
v2:
- Updated commit message.lib/librte_ethdev/rte_ethdev_version.map | 62 ++++++++++++++++---------------- lib/librte_ethdev/rte_tm.h | 33 ++++++++++++++++- 2 files changed, 64 insertions(+), 31 deletions(-)lib/librte_ethdev/rte_ethdev_version.map +23
-30@@ -135,36 +135,6 @@ DPDK_20.0 { rte_flow_isolate; rte_flow_query; rte_flow_validate; - rte_tm_capabilities_get; - rte_tm_get_number_of_leaf_nodes; - rte_tm_hierarchy_commit; - rte_tm_level_capabilities_get; - rte_tm_mark_ip_dscp; - rte_tm_mark_ip_ecn; - rte_tm_mark_vlan_dei; - rte_tm_node_add; - rte_tm_node_capabilities_get; - rte_tm_node_cman_update; - rte_tm_node_delete; - rte_tm_node_parent_update; - rte_tm_node_resume; - rte_tm_node_shaper_update; - rte_tm_node_shared_shaper_update; - rte_tm_node_shared_wred_context_update; - rte_tm_node_stats_read; - rte_tm_node_stats_update; - rte_tm_node_suspend; - rte_tm_node_type_get; - rte_tm_node_wfq_weight_mode_update; - rte_tm_node_wred_context_update; - rte_tm_shaper_profile_add; - rte_tm_shaper_profile_delete; - rte_tm_shared_shaper_add_update; - rte_tm_shared_shaper_delete; - rte_tm_shared_wred_context_add_update; - rte_tm_shared_wred_context_delete; - rte_tm_wred_profile_add; - rte_tm_wred_profile_delete; local: *; };@@ -241,6 +211,38 @@ EXPERIMENTAL { __rte_ethdev_trace_rx_burst; __rte_ethdev_trace_tx_burst; rte_flow_get_aged_flows; + + # Marked as experimental in 20.11 + rte_tm_capabilities_get; + rte_tm_get_number_of_leaf_nodes; + rte_tm_hierarchy_commit; + rte_tm_level_capabilities_get; + rte_tm_mark_ip_dscp; + rte_tm_mark_ip_ecn; + rte_tm_mark_vlan_dei; + rte_tm_node_add; + rte_tm_node_capabilities_get; + rte_tm_node_cman_update; + rte_tm_node_delete; + rte_tm_node_parent_update; + rte_tm_node_resume; + rte_tm_node_shaper_update; + rte_tm_node_shared_shaper_update; + rte_tm_node_shared_wred_context_update; + rte_tm_node_stats_read; + rte_tm_node_stats_update; + rte_tm_node_suspend; + rte_tm_node_type_get; + rte_tm_node_wfq_weight_mode_update;
lib/librte_ethdev/rte_ethdev_version.map EXPERIMENTAL { · line 246
Quoted 10 lines
lib/librte_ethdev/rte_ethdev_version.map +9
-0+ rte_tm_node_wred_context_update; + rte_tm_shaper_profile_add; + rte_tm_shaper_profile_delete; + rte_tm_shared_shaper_add_update; + rte_tm_shared_shaper_delete; + rte_tm_shared_wred_context_add_update; + rte_tm_shared_wred_context_delete; + rte_tm_wred_profile_add; + rte_tm_wred_profile_delete; };
[SNIP]
So I will re-interate what I said in April, all of these API have existed since DPDK 17.08.
I find it hard to believe they are all at imminent risk of changing to degree they _all_ warrant EXPERIMENTAL status.
Ray K
Re: [dpdk-dev] [EXT] Re: [PATCH v2] ethdev: mark all traffic manager API as experimental
Quoted 99 lines · Ray
External Email
----------------------------------------------------------------------
Quoted 93 lines · Nithin Dabilpuram
This patch marks all traffic manager API as experimental as per discussion mentioned in below thread.
Signed-off-by Nithin Dabilpuram <[email protected]>---
v2:
- Updated commit message.lib/librte_ethdev/rte_ethdev_version.map | 62 ++++++++++++++++---------------- lib/librte_ethdev/rte_tm.h | 33 ++++++++++++++++- 2 files changed, 64 insertions(+), 31 deletions(-)lib/librte_ethdev/rte_ethdev_version.map +32
-30@@ -135,36 +135,6 @@ DPDK_20.0 { rte_flow_isolate; rte_flow_query; rte_flow_validate; - rte_tm_capabilities_get; - rte_tm_get_number_of_leaf_nodes; - rte_tm_hierarchy_commit; - rte_tm_level_capabilities_get; - rte_tm_mark_ip_dscp; - rte_tm_mark_ip_ecn; - rte_tm_mark_vlan_dei; - rte_tm_node_add; - rte_tm_node_capabilities_get; - rte_tm_node_cman_update; - rte_tm_node_delete; - rte_tm_node_parent_update; - rte_tm_node_resume; - rte_tm_node_shaper_update; - rte_tm_node_shared_shaper_update; - rte_tm_node_shared_wred_context_update; - rte_tm_node_stats_read; - rte_tm_node_stats_update; - rte_tm_node_suspend; - rte_tm_node_type_get; - rte_tm_node_wfq_weight_mode_update; - rte_tm_node_wred_context_update; - rte_tm_shaper_profile_add; - rte_tm_shaper_profile_delete; - rte_tm_shared_shaper_add_update; - rte_tm_shared_shaper_delete; - rte_tm_shared_wred_context_add_update; - rte_tm_shared_wred_context_delete; - rte_tm_wred_profile_add; - rte_tm_wred_profile_delete; local: *; };@@ -241,6 +211,38 @@ EXPERIMENTAL { __rte_ethdev_trace_rx_burst; __rte_ethdev_trace_tx_burst; rte_flow_get_aged_flows; + + # Marked as experimental in 20.11 + rte_tm_capabilities_get; + rte_tm_get_number_of_leaf_nodes; + rte_tm_hierarchy_commit; + rte_tm_level_capabilities_get; + rte_tm_mark_ip_dscp; + rte_tm_mark_ip_ecn; + rte_tm_mark_vlan_dei; + rte_tm_node_add; + rte_tm_node_capabilities_get; + rte_tm_node_cman_update; + rte_tm_node_delete; + rte_tm_node_parent_update; + rte_tm_node_resume; + rte_tm_node_shaper_update; + rte_tm_node_shared_shaper_update; + rte_tm_node_shared_wred_context_update; + rte_tm_node_stats_read; + rte_tm_node_stats_update; + rte_tm_node_suspend; + rte_tm_node_type_get; + rte_tm_node_wfq_weight_mode_update; + rte_tm_node_wred_context_update; + rte_tm_shaper_profile_add; + rte_tm_shaper_profile_delete; + rte_tm_shared_shaper_add_update; + rte_tm_shared_shaper_delete; + rte_tm_shared_wred_context_add_update; + rte_tm_shared_wred_context_delete; + rte_tm_wred_profile_add; + rte_tm_wred_profile_delete; };[SNIP]
Quoted 2 lines
So I will re-interate what I said in April, all of these API have existed since DPDK 17.08.
I find it hard to believe they are all at imminent risk of changing to degree they _all_ warrant EXPERIMENTAL status.
As discussed earlier and agreed by TM and Ethdev maintainers, __rte_experimental tag was introduced several releases after TM spec was added and TM spec remained untouched ending up making it stable unintentionally.
Bruce and other maintainers pointed out that we cannot fix it as a "Fixes:" patch in order to honor ABI commitments, and suggestion was to change the complete spec back to experimental in next ABI change window and proceed with improvements that make it stable API in subsequent releases.
Quoted 2 lines
Ray K
Re: [dpdk-dev] [EXT] Re: [PATCH v2] ethdev: mark all traffic manager API as experimental
Quoted 100 lines · Nithin Dabilpuram
Quoted 99 lines · Ray
External Email
----------------------------------------------------------------------
Quoted 93 lines · Nithin Dabilpuram
This patch marks all traffic manager API as experimental as per discussion mentioned in below thread.
Signed-off-by Nithin Dabilpuram <[email protected]>---
v2:
- Updated commit message.lib/librte_ethdev/rte_ethdev_version.map | 62 ++++++++++++++++---------------- lib/librte_ethdev/rte_tm.h | 33 ++++++++++++++++- 2 files changed, 64 insertions(+), 31 deletions(-)lib/librte_ethdev/rte_ethdev_version.map +32
-30@@ -135,36 +135,6 @@ DPDK_20.0 { rte_flow_isolate; rte_flow_query; rte_flow_validate; - rte_tm_capabilities_get; - rte_tm_get_number_of_leaf_nodes; - rte_tm_hierarchy_commit; - rte_tm_level_capabilities_get; - rte_tm_mark_ip_dscp; - rte_tm_mark_ip_ecn; - rte_tm_mark_vlan_dei; - rte_tm_node_add; - rte_tm_node_capabilities_get; - rte_tm_node_cman_update; - rte_tm_node_delete; - rte_tm_node_parent_update; - rte_tm_node_resume; - rte_tm_node_shaper_update; - rte_tm_node_shared_shaper_update; - rte_tm_node_shared_wred_context_update; - rte_tm_node_stats_read; - rte_tm_node_stats_update; - rte_tm_node_suspend; - rte_tm_node_type_get; - rte_tm_node_wfq_weight_mode_update; - rte_tm_node_wred_context_update; - rte_tm_shaper_profile_add; - rte_tm_shaper_profile_delete; - rte_tm_shared_shaper_add_update; - rte_tm_shared_shaper_delete; - rte_tm_shared_wred_context_add_update; - rte_tm_shared_wred_context_delete; - rte_tm_wred_profile_add; - rte_tm_wred_profile_delete; local: *; };@@ -241,6 +211,38 @@ EXPERIMENTAL { __rte_ethdev_trace_rx_burst; __rte_ethdev_trace_tx_burst; rte_flow_get_aged_flows; + + # Marked as experimental in 20.11 + rte_tm_capabilities_get; + rte_tm_get_number_of_leaf_nodes; + rte_tm_hierarchy_commit; + rte_tm_level_capabilities_get; + rte_tm_mark_ip_dscp; + rte_tm_mark_ip_ecn; + rte_tm_mark_vlan_dei; + rte_tm_node_add; + rte_tm_node_capabilities_get; + rte_tm_node_cman_update; + rte_tm_node_delete; + rte_tm_node_parent_update; + rte_tm_node_resume; + rte_tm_node_shaper_update; + rte_tm_node_shared_shaper_update; + rte_tm_node_shared_wred_context_update; + rte_tm_node_stats_read; + rte_tm_node_stats_update; + rte_tm_node_suspend; + rte_tm_node_type_get; + rte_tm_node_wfq_weight_mode_update; + rte_tm_node_wred_context_update; + rte_tm_shaper_profile_add; + rte_tm_shaper_profile_delete; + rte_tm_shared_shaper_add_update; + rte_tm_shared_shaper_delete; + rte_tm_shared_wred_context_add_update; + rte_tm_shared_wred_context_delete; + rte_tm_wred_profile_add; + rte_tm_wred_profile_delete; };[SNIP]
Quoted 5 lines
Quoted 2 lines
So I will re-interate what I said in April, all of these API have existed since DPDK 17.08.
I find it hard to believe they are all at imminent risk of changing to degree they _all_ warrant EXPERIMENTAL status.As discussed earlier and agreed by TM and Ethdev maintainers,
__rte_experimentaltag was introduced several releases after TM spec was added and TM spec remained untouched ending up making it stable unintentionally.
We discussed it I agree, but to identify how this happened. I am not sure we all agreed it was ok to give a blanket EXPERIMENTAL.
This API has been largely unchanged for 3 years.
How can we justify keeping EXPERIMENTAL without a specific reason? Can you be more specific about planned changes?
Quoted 7 lines
Bruce and other maintainers pointed out that we cannot fix it as a "Fixes:" patch in order to honor ABI commitments, and suggestion was to change the complete spec back to experimental in next ABI change window and proceed with improvements that make it stable API in subsequent releases.
Quoted 2 lines
Ray K
Re: [dpdk-dev] [EXT] Re: [PATCH v2] ethdev: mark all traffic manager API as experimental
Quoted 109 lines · Ray
Quoted 100 lines · Nithin Dabilpuram
Quoted 99 lines · Ray
External Email
----------------------------------------------------------------------
Quoted 93 lines · Nithin Dabilpuram
This patch marks all traffic manager API as experimental as per discussion mentioned in below thread.
Signed-off-by Nithin Dabilpuram <[email protected]>---
v2:
- Updated commit message.lib/librte_ethdev/rte_ethdev_version.map | 62 ++++++++++++++++---------------- lib/librte_ethdev/rte_tm.h | 33 ++++++++++++++++- 2 files changed, 64 insertions(+), 31 deletions(-)lib/librte_ethdev/rte_ethdev_version.map +32
-30@@ -135,36 +135,6 @@ DPDK_20.0 { rte_flow_isolate; rte_flow_query; rte_flow_validate; - rte_tm_capabilities_get; - rte_tm_get_number_of_leaf_nodes; - rte_tm_hierarchy_commit; - rte_tm_level_capabilities_get; - rte_tm_mark_ip_dscp; - rte_tm_mark_ip_ecn; - rte_tm_mark_vlan_dei; - rte_tm_node_add; - rte_tm_node_capabilities_get; - rte_tm_node_cman_update; - rte_tm_node_delete; - rte_tm_node_parent_update; - rte_tm_node_resume; - rte_tm_node_shaper_update; - rte_tm_node_shared_shaper_update; - rte_tm_node_shared_wred_context_update; - rte_tm_node_stats_read; - rte_tm_node_stats_update; - rte_tm_node_suspend; - rte_tm_node_type_get; - rte_tm_node_wfq_weight_mode_update; - rte_tm_node_wred_context_update; - rte_tm_shaper_profile_add; - rte_tm_shaper_profile_delete; - rte_tm_shared_shaper_add_update; - rte_tm_shared_shaper_delete; - rte_tm_shared_wred_context_add_update; - rte_tm_shared_wred_context_delete; - rte_tm_wred_profile_add; - rte_tm_wred_profile_delete; local: *; };@@ -241,6 +211,38 @@ EXPERIMENTAL { __rte_ethdev_trace_rx_burst; __rte_ethdev_trace_tx_burst; rte_flow_get_aged_flows; + + # Marked as experimental in 20.11 + rte_tm_capabilities_get; + rte_tm_get_number_of_leaf_nodes; + rte_tm_hierarchy_commit; + rte_tm_level_capabilities_get; + rte_tm_mark_ip_dscp; + rte_tm_mark_ip_ecn; + rte_tm_mark_vlan_dei; + rte_tm_node_add; + rte_tm_node_capabilities_get; + rte_tm_node_cman_update; + rte_tm_node_delete; + rte_tm_node_parent_update; + rte_tm_node_resume; + rte_tm_node_shaper_update; + rte_tm_node_shared_shaper_update; + rte_tm_node_shared_wred_context_update; + rte_tm_node_stats_read; + rte_tm_node_stats_update; + rte_tm_node_suspend; + rte_tm_node_type_get; + rte_tm_node_wfq_weight_mode_update; + rte_tm_node_wred_context_update; + rte_tm_shaper_profile_add; + rte_tm_shaper_profile_delete; + rte_tm_shared_shaper_add_update; + rte_tm_shared_shaper_delete; + rte_tm_shared_wred_context_add_update; + rte_tm_shared_wred_context_delete; + rte_tm_wred_profile_add; + rte_tm_wred_profile_delete; };[SNIP]
Quoted 5 lines
Quoted 2 lines
So I will re-interate what I said in April, all of these API have existed since DPDK 17.08.
I find it hard to believe they are all at imminent risk of changing to degree they _all_ warrant EXPERIMENTAL status.As discussed earlier and agreed by TM and Ethdev maintainers,
__rte_experimentaltag was introduced several releases after TM spec was added and TM spec remained untouched ending up making it stable unintentionally.
Quoted 6 lines
We discussed it I agree, but to identify how this happened. I am not sure we all agreed it was ok to give a blanket EXPERIMENTAL.
This API has been largely unchanged for 3 years.
How can we justify keeping EXPERIMENTAL without a specific reason? Can you be more specific about planned changes?
Basically the changes atleast which initiated this discussion were
#1 Support to configure shaper in pkt mode that helps ratelimiting in PPS(Packets per Sec) as opposed to BPS(Bits per Sec). Needs change to a lot of existing tm param and capability structs.
#2 Support dynamic offload flags based Tx offload for tm packet marking.
#3 Support TM node color stats that report per tm color(red, green, yellow) pkt stats.
All the above three changes though add significant features and doesn't break existing PMD's.
Quoted 8 lines
Quoted 8 lines
Bruce and other maintainers pointed out that we cannot fix it as a "Fixes:" patch in order to honor ABI commitments, and suggestion was to change the complete spec back to experimental in next ABI change window and proceed with improvements that make it stable API in subsequent releases.
Quoted 2 lines
Ray K
Re: [dpdk-dev] [PATCH v2] ethdev: mark all traffic manager API as experimental
In reply to Nithin DabilpuramQuoted 10 lines · Nithin Dabilpuram
This patch marks all traffic manager API as experimental as per discussion mentioned in below thread.
https://mails.dpdk.org/archives/dev/2020-April/165364.html
Signed-off-by Nithin Dabilpuram <[email protected]>---
v2:
- Updated commit message.
Hi Nithin Kumar,
Perhaps there was a misunderstanding, the paragraph in the deprecation note documents about making tm APIs experimental needs to be removed, since it won't be valid anymore after this patch.
And best place to remove that note is this patch.
Re: [dpdk-dev] [PATCH v2] ethdev: mark all traffic manager API as experimental
Quoted 28 lines
-----Original Message-----
From: Ferruh Yigit <[email protected]>
Sent: Thursday, September 10, 2020 9:36 AM
To: Nithin Dabilpuram <[email protected]>; Richardson, Bruce <[email protected]>; Dumitrescu, Cristian <[email protected]>; [email protected]; [email protected]; Singh, Jasvinder <[email protected]>; [email protected]; Kinsella, Ray <[email protected]>; [email protected]; [email protected]; [email protected]; Ray Kinsella <[email protected]>
Cc: [email protected]; [email protected]
Subject: Re: [PATCH v2] ethdev: mark all traffic manager API as experimentalQuoted 10 lines · Nithin Dabilpuram
This patch marks all traffic manager API as experimental as per discussion mentioned in below thread.
https://mails.dpdk.org/archives/dev/2020-April/165364.html
Signed-off-by Nithin Dabilpuram <[email protected]>---
v2:
- Updated commit message.
Quoted 8 lines
Hi Nithin Kumar,
Perhaps there was a misunderstanding, the paragraph in the deprecation note
documents about making tm APIs experimental needs to be removed, since it won't
be valid anymore after this patch.
And best place to remove that note is this patch.
And also please include my ack from V1.
Re: [dpdk-dev] [EXT] RE: [PATCH v2] ethdev: mark all traffic manager API as experimental
Quoted 33 lines · Cristian
External Email
----------------------------------------------------------------------
Quoted 28 lines
-----Original Message-----
From: Ferruh Yigit <[email protected]>
Sent: Thursday, September 10, 2020 9:36 AM
To: Nithin Dabilpuram <[email protected]>; Richardson, Bruce <[email protected]>; Dumitrescu, Cristian <[email protected]>; [email protected]; [email protected]; Singh, Jasvinder <[email protected]>; [email protected]; Kinsella, Ray <[email protected]>; [email protected]; [email protected]; [email protected]; Ray Kinsella <[email protected]>
Cc: [email protected]; [email protected]
Subject: Re: [PATCH v2] ethdev: mark all traffic manager API as experimentalQuoted 10 lines · Nithin Dabilpuram
This patch marks all traffic manager API as experimental as per discussion mentioned in below thread.
Signed-off-by Nithin Dabilpuram <[email protected]>---
v2:
- Updated commit message.Hi Nithin Kumar,
Quoted 8 lines
Quoted 6 lines
Perhaps there was a misunderstanding, the paragraph in the deprecation note
documents about making tm APIs experimental needs to be removed, since it won't
be valid anymore after this patch.
And best place to remove that note is this patch.And also please include my ack from V1.
Ack, sorry for missing that.
Re: [dpdk-dev] [EXT] Re: [PATCH v2] ethdev: mark all traffic manager API as experimental
In reply to Ferruh YigitQuoted 16 lines · Ferruh Yigit
External Email
----------------------------------------------------------------------
Quoted 10 lines · Nithin Dabilpuram
This patch marks all traffic manager API as experimental as per discussion mentioned in below thread.
Signed-off-by Nithin Dabilpuram <[email protected]>---
v2:
- Updated commit message.
Quoted 6 lines
Hi Nithin Kumar,
Perhaps there was a misunderstanding, the paragraph in the deprecation note documents about making tm APIs experimental needs to be removed, since it won't be valid anymore after this patch.
And best place to remove that note is this patch.
Apologies for misunderstanding your statement. Will send a V3 with the same.
PATCH v3 1/1 ethdev: mark all traffic manager API as experimental
In reply to Nithin DabilpuramThis patch marks all traffic manager API as experimental as per deprecation notice[1] and discussion[2] mentioned in following threads.
[1] https://mails.dpdk.org/archives/dev/2020-May/166221.html
[2] https://mails.dpdk.org/archives/dev/2020-April/165364.html
--- doc/guides/rel_notes/deprecation.rst | 7 ---- lib/librte_ethdev/rte_ethdev_version.map | 62 ++++++++++++++++---------------- lib/librte_ethdev/rte_tm.h | 33 ++++++++++++++++- 3 files changed, 64 insertions(+), 38 deletions(-)
doc/guides/rel_notes/deprecation.rst +0 -7
@@ -237,13 +237,6 @@ Deprecation Notices following the IPv6 header, as proposed in RFC https://mails.dpdk.org/archives/dev/2020-August/177257.html. -* traffic manager: All traffic manager API's in ``rte_tm.h`` were mistakenly made - ABI stable in the v19.11 release. The TM maintainer and other contributors have - agreed to keep the TM APIs as experimental in expectation of additional spec - improvements. Therefore, all APIs in ``rte_tm.h`` will be marked back as - experimental in v20.11 DPDK release. For more details, please see `the thread - <https://mails.dpdk.org/archives/dev/2020-April/164970.html>`_. - * pmd_dpaa: The API ``rte_pmd_dpaa_set_tx_loopback`` will have extended ``port_id`` definition from ``uint8_t`` to ``uint16_t``.
lib/librte_ethdev/rte_ethdev_version.map +32 -30
74 lines not on this page · raw message
lib/librte_ethdev/rte_tm.h +32 -1
@@ -16,7 +16,8 @@* traffic shaping, congestion management, packet marking, etc. * * @warning -* @b EXPERIMENTAL: this API may change without prior notice +* @b EXPERIMENTAL: +* All functions in this file may be changed or removed without prior notice. */ #include <stdint.h>
@@ -1050,6 +1051,7 @@ struct rte_tm_error {* @return * 0 on success, non-zero error code otherwise. */ +__rte_experimental int rte_tm_get_number_of_leaf_nodes(uint16_t port_id, uint32_t *n_leaf_nodes,
@@ -1074,6 +1076,7 @@ rte_tm_get_number_of_leaf_nodes(uint16_t port_id,* @return * 0 on success, non-zero error code otherwise. */ +__rte_experimental int rte_tm_node_type_get(uint16_t port_id, uint32_t node_id,
@@ -1092,6 +1095,7 @@ rte_tm_node_type_get(uint16_t port_id,* @return * 0 on success, non-zero error code otherwise. */ +__rte_experimental int rte_tm_capabilities_get(uint16_t port_id, struct rte_tm_capabilities *cap,
@@ -1112,6 +1116,7 @@ rte_tm_capabilities_get(uint16_t port_id,* @return * 0 on success, non-zero error code otherwise. */ +__rte_experimental int rte_tm_level_capabilities_get(uint16_t port_id, uint32_t level_id,
@@ -1132,6 +1137,7 @@ rte_tm_level_capabilities_get(uint16_t port_id,* @return * 0 on success, non-zero error code otherwise. */ +__rte_experimental int rte_tm_node_capabilities_get(uint16_t port_id, uint32_t node_id,
@@ -1157,6 +1163,7 @@ rte_tm_node_capabilities_get(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_n_max */ +__rte_experimental int rte_tm_wred_profile_add(uint16_t port_id, uint32_t wred_profile_id,
@@ -1180,6 +1187,7 @@ rte_tm_wred_profile_add(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_n_max */ +__rte_experimental int rte_tm_wred_profile_delete(uint16_t port_id, uint32_t wred_profile_id,
@@ -1211,6 +1219,7 @@ rte_tm_wred_profile_delete(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_shared_n_max */ +__rte_experimental int rte_tm_shared_wred_context_add_update(uint16_t port_id, uint32_t shared_wred_context_id,
@@ -1235,6 +1244,7 @@ rte_tm_shared_wred_context_add_update(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_shared_n_max */ +__rte_experimental int rte_tm_shared_wred_context_delete(uint16_t port_id, uint32_t shared_wred_context_id,
@@ -1259,6 +1269,7 @@ rte_tm_shared_wred_context_delete(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_n_max */ +__rte_experimental int rte_tm_shaper_profile_add(uint16_t port_id, uint32_t shaper_profile_id,
@@ -1282,6 +1293,7 @@ rte_tm_shaper_profile_add(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_n_max */ +__rte_experimental int rte_tm_shaper_profile_delete(uint16_t port_id, uint32_t shaper_profile_id,
@@ -1311,6 +1323,7 @@ rte_tm_shaper_profile_delete(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_shared_n_max */ +__rte_experimental int rte_tm_shared_shaper_add_update(uint16_t port_id, uint32_t shared_shaper_id,
@@ -1334,6 +1347,7 @@ rte_tm_shared_shaper_add_update(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_shared_n_max */ +__rte_experimental int rte_tm_shared_shaper_delete(uint16_t port_id, uint32_t shared_shaper_id,
@@ -1402,6 +1416,7 @@ rte_tm_shared_shaper_delete(uint16_t port_id,* @see RTE_TM_NODE_LEVEL_ID_ANY * @see struct rte_tm_capabilities */ +__rte_experimental int rte_tm_node_add(uint16_t port_id, uint32_t node_id,
@@ -1435,6 +1450,7 @@ rte_tm_node_add(uint16_t port_id,* * @see RTE_TM_UPDATE_NODE_ADD_DELETE */ +__rte_experimental int rte_tm_node_delete(uint16_t port_id, uint32_t node_id,
@@ -1459,6 +1475,7 @@ rte_tm_node_delete(uint16_t port_id,* @see rte_tm_node_resume() * @see RTE_TM_UPDATE_NODE_SUSPEND_RESUME */ +__rte_experimental int rte_tm_node_suspend(uint16_t port_id, uint32_t node_id,
@@ -1482,6 +1499,7 @@ rte_tm_node_suspend(uint16_t port_id,* @see rte_tm_node_suspend() * @see RTE_TM_UPDATE_NODE_SUSPEND_RESUME */ +__rte_experimental int rte_tm_node_resume(uint16_t port_id, uint32_t node_id,
@@ -1523,6 +1541,7 @@ rte_tm_node_resume(uint16_t port_id,* @see rte_tm_node_add() * @see rte_tm_node_delete() */ +__rte_experimental int rte_tm_hierarchy_commit(uint16_t port_id, int clear_on_fail,
@@ -1563,6 +1582,7 @@ rte_tm_hierarchy_commit(uint16_t port_id,* @see RTE_TM_UPDATE_NODE_PARENT_KEEP_LEVEL * @see RTE_TM_UPDATE_NODE_PARENT_CHANGE_LEVEL */ +__rte_experimental int rte_tm_node_parent_update(uint16_t port_id, uint32_t node_id,
@@ -1592,6 +1612,7 @@ rte_tm_node_parent_update(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_private_n_max */ +__rte_experimental int rte_tm_node_shaper_update(uint16_t port_id, uint32_t node_id,
@@ -1619,6 +1640,7 @@ rte_tm_node_shaper_update(uint16_t port_id,* * @see struct rte_tm_capabilities::shaper_shared_n_max */ +__rte_experimental int rte_tm_node_shared_shaper_update(uint16_t port_id, uint32_t node_id,
@@ -1646,6 +1668,7 @@ rte_tm_node_shared_shaper_update(uint16_t port_id,* @see enum rte_tm_stats_type * @see RTE_TM_UPDATE_NODE_STATS */ +__rte_experimental int rte_tm_node_stats_update(uint16_t port_id, uint32_t node_id,
@@ -1674,6 +1697,7 @@ rte_tm_node_stats_update(uint16_t port_id,* @see RTE_TM_UPDATE_NODE_WFQ_WEIGHT_MODE * @see RTE_TM_UPDATE_NODE_N_SP_PRIORITIES */ +__rte_experimental int rte_tm_node_wfq_weight_mode_update(uint16_t port_id, uint32_t node_id,
@@ -1697,6 +1721,7 @@ rte_tm_node_wfq_weight_mode_update(uint16_t port_id,* * @see RTE_TM_UPDATE_NODE_CMAN */ +__rte_experimental int rte_tm_node_cman_update(uint16_t port_id, uint32_t node_id,
@@ -1721,6 +1746,7 @@ rte_tm_node_cman_update(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_private_n_max */ +__rte_experimental int rte_tm_node_wred_context_update(uint16_t port_id, uint32_t node_id,
@@ -1746,6 +1772,7 @@ rte_tm_node_wred_context_update(uint16_t port_id,* * @see struct rte_tm_capabilities::cman_wred_context_shared_n_max */ +__rte_experimental int rte_tm_node_shared_wred_context_update(uint16_t port_id, uint32_t node_id,
@@ -1778,6 +1805,7 @@ rte_tm_node_shared_wred_context_update(uint16_t port_id,* * @see enum rte_tm_stats_type */ +__rte_experimental int rte_tm_node_stats_read(uint16_t port_id, uint32_t node_id,
@@ -1815,6 +1843,7 @@ rte_tm_node_stats_read(uint16_t port_id,* * @see struct rte_tm_capabilities::mark_vlan_dei_supported */ +__rte_experimental int rte_tm_mark_vlan_dei(uint16_t port_id, int mark_green,
@@ -1865,6 +1894,7 @@ rte_tm_mark_vlan_dei(uint16_t port_id,* @see struct rte_tm_capabilities::mark_ip_ecn_tcp_supported * @see struct rte_tm_capabilities::mark_ip_ecn_sctp_supported */ +__rte_experimental int rte_tm_mark_ip_ecn(uint16_t port_id, int mark_green,
@@ -1913,6 +1943,7 @@ rte_tm_mark_ip_ecn(uint16_t port_id,* * @see struct rte_tm_capabilities::mark_ip_dscp_supported */ +__rte_experimental int rte_tm_mark_ip_dscp(uint16_t port_id, int mark_green,
Signature · 1 line
2.8.4
Re: [dpdk-dev] [PATCH v3] ethdev: mark all traffic manager API as experimental
Quoted 9 lines · Nithin Dabilpuram
This patch marks all traffic manager API as experimental as per deprecation notice[1] and discussion[2] mentioned in following threads.
[1] https://mails.dpdk.org/archives/dev/2020-May/166221.html
[2] https://mails.dpdk.org/archives/dev/2020-April/165364.htmlSigned-off-by Nithin Dabilpuram <[email protected]>
Applied to dpdk-next-net/main, thanks.
I see there is discussion on the experimental status of the APIs, I am proceeding with the patchset since there is an existing deprecation notice for it, but if some APIs decided to be non experimental that change can be done incrementally on top of this.