DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jasvinder Singh <jasvinder.singh@intel.com>
To: dev@dpdk.org
Cc: cristian.dumitrescu@intel.com
Subject: [dpdk-dev] [PATCH] doc: add deprecation notice for sched changes
Date: Wed, 24 Apr 2019 13:37:17 +0100	[thread overview]
Message-ID: <20190424123717.123541-1-jasvinder.singh@intel.com> (raw)
Message-ID: <20190424123717.Y055UMde0WeW67axBNJz7gkpgX22hvibUEvFA-20t6Q@z> (raw)

Add deprecation note for making changes in data structures, APIs
and macros in order to have more traffic classes, flexible
mapping of pipe queues to traffic classes, subport level
configuration of pipes and queues, etc. These changes are aligned
to improvements suggested in the RFC-
https://mails.dpdk.org/archives/dev/2018-November/120035.html

Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@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 b47c8c254..051ab5c2a 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -79,6 +79,12 @@ Deprecation Notices
 
   The field would be added in v19.08.
 
+* sched: To allow more traffic classes, flexible mapping of pipe queues to
+  traffic classes, and subport level configuration of pipes and queues
+  changes will be made to macros, data structures and API functions defined
+  in "rte_sched.h". These changes are aligned to improvements suggested in the
+  RFC https://mails.dpdk.org/archives/dev/2018-November/120035.html.
+
 * cryptodev: the ``uint8_t *data`` member of ``key`` structure in the xforms
   structure (``rte_crypto_cipher_xform``, ``rte_crypto_auth_xform``, and
   ``rte_crypto_aead_xform``) will be changed to ``const uint8_t *data``.
-- 
2.17.1


             reply	other threads:[~2019-04-24 12:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 12:37 Jasvinder Singh [this message]
2019-04-24 12:37 ` Jasvinder Singh
2019-04-29 10:31 ` Mohammad Abdul Awal
2019-04-29 10:31   ` Mohammad Abdul Awal
2019-05-13 13:56   ` Thomas Monjalon
2019-05-13 13:56     ` Thomas Monjalon
2019-05-13 13:59     ` Singh, Jasvinder
2019-05-13 13:59       ` Singh, Jasvinder
2019-05-13 14:12       ` Thomas Monjalon
2019-05-13 14:12         ` Thomas Monjalon
2019-05-13 21:31         ` Thomas Monjalon
2019-05-13 21:31           ` Thomas Monjalon
2019-04-30 15:18 ` Pattan, Reshma
2019-04-30 15:18   ` Pattan, Reshma
2020-07-16 10:28 Savinay Dharmappa

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=20190424123717.123541-1-jasvinder.singh@intel.com \
    --to=jasvinder.singh@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    /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).