From: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
To: Jasvinder Singh <jasvinder.singh@intel.com>, dev@dpdk.org
Cc: cristian.dumitrescu@intel.com
Subject: Re: [dpdk-dev] [PATCH] doc: deprecation notice for sched API change
Date: Wed, 21 Nov 2018 09:39:16 +0000 [thread overview]
Message-ID: <533a742b-be09-8bcc-d469-7d29f8cf5018@intel.com> (raw)
In-Reply-To: <20181114153642.88575-1-jasvinder.singh@intel.com>
On 14/11/2018 15:36, Jasvinder Singh wrote:
> There will be change in API functions because of mbuf sched field
> updates, outlined in deprecation note of mbuf->hash.sched.
>
> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 34b28234c..b54598d07 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -34,6 +34,11 @@ Deprecation Notices
> is defined in librte_sched in a non-generic way. The new generic format
> will contain: queue ID, traffic class, color. Field size will not change.
>
> +* sched: Some API functions will change prototype due to the above
> + deprecation note for mbuf->hash.sched, e.g. rte_sched_port_pkt_write() and
> + rte_sched_port_pkt_read() will likely have an additional parameter
> + of type struct rte_sched_port.
> +
> * mbuf: the macro ``RTE_MBUF_INDIRECT()`` will be removed in v18.08 or later and
> replaced with ``RTE_MBUF_CLONED()`` which is already added in v18.05. As
> ``EXT_ATTACHED_MBUF`` is newly introduced in v18.05, ``RTE_MBUF_INDIRECT()``
Acked-by: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
next prev parent reply other threads:[~2018-11-21 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 15:36 Jasvinder Singh
2018-11-16 16:10 ` Pattan, Reshma
2018-11-21 9:39 ` Mohammad Abdul Awal [this message]
2018-11-24 18:13 ` 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=533a742b-be09-8bcc-d469-7d29f8cf5018@intel.com \
--to=mohammad.abdul.awal@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@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).