doc: deprecation notice for sched changes

Message ID 20190128112756.12516-1-reshma.pattan@intel.com (mailing list archive)
State Rejected, archived
Delegated to: Thomas Monjalon
Headers
Series doc: deprecation notice for sched changes |

Checks

Context Check Description
ci/checkpatch success coding style OK
ci/Intel-compilation success Compilation OK

Commit Message

Pattan, Reshma Jan. 28, 2019, 11:27 a.m. UTC
  From: Jasvinder Singh <jasvinder.singh@intel.com>

Add deprecation note for making changes in data structures, APIs and
macros in order to increase the traffic classes, flexible mapping of
pipe queues to traffic classes, subport level configuration of
pipes, queues sizes, etc.

Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
Cc: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
---
 doc/guides/rel_notes/deprecation.rst | 7 +++++++
 1 file changed, 7 insertions(+)
  

Comments

Pattan, Reshma Jan. 28, 2019, 4:28 p.m. UTC | #1
Hi,

More  details needs to be added to deprecation note which are not clear yet, so self NACK.

Thanks,
Reshma

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Reshma Pattan
> Sent: Monday, January 28, 2019 11:28 AM
> To: dev@dpdk.org
> Cc: Singh, Jasvinder <jasvinder.singh@intel.com>; Dumitrescu, Cristian
> <cristian.dumitrescu@intel.com>
> Subject: [dpdk-dev] [PATCH] doc: deprecation notice for sched changes
> 
> From: Jasvinder Singh <jasvinder.singh@intel.com>
> 
> Add deprecation note for making changes in data structures, APIs and macros in
> order to increase the traffic classes, flexible mapping of pipe queues to traffic
> classes, subport level configuration of pipes, queues sizes, etc.
> 
> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> Cc: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> ---
>  doc/guides/rel_notes/deprecation.rst | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index f9a1f8188..22a3ecb35 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -14,6 +14,13 @@ Deprecation Notices
>  * kvargs: The function ``rte_kvargs_process`` will get a new parameter
>    for returning key match count. It will ease handling of no-match case.
> 
> +* sched: The data structures specifying port, subport and pipe
> +parameters, stats,
> +  API functions to configure hierarchy, collecting stats, and computing
> +memory
> +  footprint will be changed to support more number of traffic classes
> +(TCs),
> +  flexible mapping of the pipe queues to traffic classes, subport level
> +  configration of the pipes, etc. In addition, the macros defined for
> +building
> +  the hierarchy will be reworked to support the flexibility.
> +
>  * eal: both declaring and identifying devices will be streamlined in v18.11.
>    New functions will appear to query a specific port from buses, classes of
>    device and device drivers. Device declaration will be made coherent with the
> --
> 2.17.1
  

Patch

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index f9a1f8188..22a3ecb35 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -14,6 +14,13 @@  Deprecation Notices
 * kvargs: The function ``rte_kvargs_process`` will get a new parameter
   for returning key match count. It will ease handling of no-match case.
 
+* sched: The data structures specifying port, subport and pipe parameters, stats,
+  API functions to configure hierarchy, collecting stats, and computing memory
+  footprint will be changed to support more number of traffic classes (TCs),
+  flexible mapping of the pipe queues to traffic classes, subport level
+  configration of the pipes, etc. In addition, the macros defined for building
+  the hierarchy will be reworked to support the flexibility.
+
 * eal: both declaring and identifying devices will be streamlined in v18.11.
   New functions will appear to query a specific port from buses, classes of
   device and device drivers. Device declaration will be made coherent with the