From: yang_y_yi@163.com
To: dev@dpdk.org
Cc: jiayu.hu@intel.com, thomas@monjalon.net, yangyi01@inspur.com,
yang_y_yi@163.com, Ray Kinsella <mdr@ashroe.eu>,
Neil Horman <nhorman@tuxdriver.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Subject: [dpdk-dev] [PATCH] doc: announce deprecation of rte_mbuf_extbuf_free_callback_t
Date: Thu, 30 Jul 2020 20:55:54 +0800 [thread overview]
Message-ID: <20200730125555.43908-1-yang_y_yi@163.com> (raw)
From: Yi Yang <yangyi01@inspur.com>
typedef rte_mbuf_extbuf_free_callback_t will be deprecated
in 20.08 release.
Signed-off-by: Yi Yang <yangyi01@inspur.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 99c9806..df60e06 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -135,6 +135,14 @@ Deprecation Notices
will be removed in 20.11. It will be replaced with ``refcnt`` of type
``uint16_t``.
+* rte_mbuf_ext_shared_info: typedef of ``free_cb`` member in structure
+ ``rte_mbuf_ext_shared_info`` ``rte_mbuf_extbuf_free_callback_t`` will be
+ changed to adapt to GSO case, new typedef will be
+ ``void (*rte_mbuf_extbuf_free_callback_t)(struct rte_mbuf *, void *)``,
+ it is impossible to free original owner mbuf of shinfo by ``free_cb`` and
+ keep compatible with non-GSO case at the same time without this change.
+ It will be deprecated in 20.08.
+
* metrics: The function ``rte_metrics_init`` will have a non-void return
in order to notify errors instead of calling ``rte_exit``.
--
1.8.3.1
reply other threads:[~2020-07-30 12:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200730125555.43908-1-yang_y_yi@163.com \
--to=yang_y_yi@163.com \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.com \
--cc=thomas@monjalon.net \
--cc=yangyi01@inspur.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).