DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Singh, Jasvinder" <jasvinder.singh@intel.com>
To: "Liguzinski, WojciechX" <wojciechx.liguzinski@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: "Dharmappa, Savinay" <Savinay.Dharmappa@intel.com>,
	"Ajmera, Megha" <megha.ajmera@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: add deprecation notice for PIE active queue management changes
Date: Fri, 6 Aug 2021 14:45:25 +0000	[thread overview]
Message-ID: <BN9PR11MB5258D9B8C5D65A3A67364685E0F39@BN9PR11MB5258.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210602121200.4649-1-wojciechx.liguzinski@intel.com>



> -----Original Message-----
> From: Liguzinski, WojciechX <wojciechx.liguzinski@intel.com>
> Sent: Wednesday, June 2, 2021 1:12 PM
> To: dev@dpdk.org; Singh, Jasvinder <jasvinder.singh@intel.com>;
> Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Cc: Dharmappa, Savinay <Savinay.Dharmappa@intel.com>; Ajmera, Megha
> <megha.ajmera@intel.com>
> Subject: [PATCH v2] doc: add deprecation notice for PIE active queue
> management changes
> 
> Add deprecation note for making changes related to implementation of PIE
> based active queue management support to DPDK scheduler library.
> These changes are aligned as suggested in the RFC[1].
> 
> https://mails.dpdk.org/archives/dev/2021-May/210067.html
> 
> Signed-off-by: Liguzinski, WojciechX <wojciechx.liguzinski@intel.com>
> ---
>  doc/guides/rel_notes/deprecation.rst | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index 9584d6bfd7..113b5b55c1 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -141,6 +141,14 @@ Deprecation Notices
>    in "rte_sched.h". These changes are aligned to improvements suggested in
> the
>    RFC https://mails.dpdk.org/archives/dev/2018-November/120035.html.
> 
> +* sched: To add PIE based active queue management support to DPDK
> +scheduler
> +  library, changes will be made to data structures
> +  ``rte_sched_subport_params``, ``rte_sched_subport_stats``,
> +  ``rte_sched_queue_stats``, ``rte_sched_queue_extra``,
> ``rte_sched_subport``.
> +  New structures are introduced for PIE ``rte_pie_params``,
> +``rte_pie_config``,
> +  ``rte_pie``. These changes are aligned to improvements suggested in
> +the RFC
> +  https://mails.dpdk.org/archives/dev/2021-May/210067.html.
> +
>  * metrics: The function ``rte_metrics_init`` will have a non-void return
>    in order to notify errors instead of calling ``rte_exit``.
> 
> --
> 2.17.1

Acked-by: Jasvinder Singh <jasvinder.singh@intel.com>



      reply	other threads:[~2021-08-06 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 12:19 [dpdk-dev] [PATCH v1] " Liguzinski, WojciechX
2021-06-02 12:12 ` [dpdk-dev] [PATCH v2] " Liguzinski, WojciechX
2021-08-06 14:45   ` Singh, Jasvinder [this message]

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=BN9PR11MB5258D9B8C5D65A3A67364685E0F39@BN9PR11MB5258.namprd11.prod.outlook.com \
    --to=jasvinder.singh@intel.com \
    --cc=Savinay.Dharmappa@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=megha.ajmera@intel.com \
    --cc=wojciechx.liguzinski@intel.com \
    /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).