From: "Shetty, Praveen" <praveen.shetty@intel.com>
To: "Dharmappa, Savinay" <savinay.dharmappa@intel.com>,
"Dharmappa, Savinay" <savinay.dharmappa@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: add deprecation notice for sched changes
Date: Mon, 27 Jul 2020 11:16:42 +0000 [thread overview]
Message-ID: <CY4PR1101MB2326A79F8D2EFF923966E1929D720@CY4PR1101MB2326.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1594905931-447219-1-git-send-email-savinay.dharmappa@intel.com>
-----Original Message-----
From: dev <dev-bounces@dpdk.org> On Behalf Of Savinay Dharmappa
Sent: Thursday, July 16, 2020 6:56 PM
To: Dharmappa, Savinay <savinay.dharmappa@intel.com>; dev@dpdk.org
Cc: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Singh, Jasvinder <jasvinder.singh@intel.com>
Subject: [dpdk-dev] [PATCH v2] 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>
Signed-off-by: Jasvinder Singh <jasvinder.singh@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 a58a179..14df5df 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -129,6 +129,12 @@ 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 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``.
Acked-by: Praveen Shetty <praveen.shetty@intel.com>
--
2.7.4
next prev parent reply other threads:[~2020-07-27 11:16 UTC|newest]
Thread overview: 10+ 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 [this message]
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
2020-08-06 14:16 ` Thomas Monjalon
2020-08-07 22:49 ` Thomas Monjalon
2020-07-16 13:21 [dpdk-dev] [PATCH v2] " Savinay Dharmappa
2020-07-23 11:23 ` Singh, Jasvinder
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=CY4PR1101MB2326A79F8D2EFF923966E1929D720@CY4PR1101MB2326.namprd11.prod.outlook.com \
--to=praveen.shetty@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=savinay.dharmappa@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).