DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Pai G, Sunil" <sunil.pai.g@intel.com>
To: "Dharmappa, Savinay" <savinay.dharmappa@intel.com>,
	"Dharmappa, Savinay" <savinay.dharmappa@intel.com>,
	"Singh, Jasvinder" <jasvinder.singh@intel.com>,
	"Shetty, Praveen" <praveen.shetty@intel.com>,
	"Tummala, Sivaprasad" <sivaprasad.tummala@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Subject: Re: [dpdk-dev] [PATCH v4] doc: add deprecation notice for sched changes
Date: Tue, 4 Aug 2020 14:14:15 +0000	[thread overview]
Message-ID: <MWHPR11MB180515A5B850A0E23DEB35BFBD4A0@MWHPR11MB1805.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1596020881-409466-1-git-send-email-savinay.dharmappa@intel.com>

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Savinay Dharmappa
> Sent: Wednesday, July 29, 2020 4:38 PM
> To: Dharmappa, Savinay <savinay.dharmappa@intel.com>; Singh, Jasvinder
> <jasvinder.singh@intel.com>; Shetty, Praveen <praveen.shetty@intel.com>;
> Tummala, Sivaprasad <sivaprasad.tummala@intel.com>; dev@dpdk.org
> Cc: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Subject: [dpdk-dev] [PATCH v4] doc: add deprecation notice for sched changes
> 
> Add deprecation note for making changes in data structures and APIs in order to
> allow dynamic configuration of subport bandwidth profile.
> These changes are aligned as suggested in the RFC[1].
> 
> https://mails.dpdk.org/archives/dev/2020-July/175161.html
> 
> Signed-off-by: Savinay Dharmappa <savinay.dharmappa@intel.com>
> Acked-by: Jasvinder Singh <jasvinder.singh@intel.com>
> Acked-by: Praveen Shetty <praveen.shetty@intel.com>
> ---
>  doc/guides/rel_notes/deprecation.rst | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index 99c9806..9a9ecb1 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -135,6 +135,12 @@ Deprecation Notices
>    will be removed in 20.11. It will be replaced with ``refcnt`` of type
>    ``uint16_t``.
> 
> +* sched: To allow dynamic configuration of the subport bandwidth
> +profile,
> +  changes will be made to data structures ``rte_sched_subport_params``
> +  ``rte_sched_port_params`` and new data structure, API functions will
> +be
> +  defined in "rte_sched.h". These changes are aligned as suggested in
> +the
> +  RFC https://mails.dpdk.org/archives/dev/2020-July/175161.html
> +
>  * metrics: The function ``rte_metrics_init`` will have a non-void return
>    in order to notify errors instead of calling ``rte_exit``.
> 
> --
> 2.7.4

Acked-by: Sunil Pai G <sunil.pai.g@intel.com>

  reply	other threads:[~2020-08-04 14:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 10:28 [dpdk-dev] [PATCH] " Savinay Dharmappa
2020-07-16 13:25 ` [dpdk-dev] [PATCH v2] " Savinay Dharmappa
2020-07-27 11:16   ` Shetty, Praveen
2020-07-29  5:13   ` [dpdk-dev] [PATCH v3] " Savinay Dharmappa
2020-07-29 11:08     ` [dpdk-dev] [PATCH v4] " Savinay Dharmappa
2020-08-04 14:14       ` Pai G, Sunil [this message]
2020-08-06 14:16         ` Thomas Monjalon
2020-08-07 22:49           ` Thomas Monjalon

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=MWHPR11MB180515A5B850A0E23DEB35BFBD4A0@MWHPR11MB1805.namprd11.prod.outlook.com \
    --to=sunil.pai.g@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=jasvinder.singh@intel.com \
    --cc=praveen.shetty@intel.com \
    --cc=savinay.dharmappa@intel.com \
    --cc=sivaprasad.tummala@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).