From: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
To: <dev@dpdk.org>
Cc: <ferruh.yigit@amd.com>, <bruce.richardson@intel.com>,
<david.marchand@redhat.com>, <thomas@monjalon.net>
Subject: [PATCH] doc: deprecation notice to add callback data to rte_event_fp_ops
Date: Wed, 12 Jul 2023 10:30:50 -0700 [thread overview]
Message-ID: <20230712173050.599482-1-sivaprasad.tummala@amd.com> (raw)
Deprecation notice to add "rte_eventdev_port_data" field to
``rte_event_fp_ops`` for callback support.
Signed-off-by: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
---
doc/guides/rel_notes/deprecation.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 8e1cdd677a..2c69338818 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -133,6 +133,10 @@ Deprecation Notices
``rte_cryptodev_get_auth_algo_string``, ``rte_cryptodev_get_aead_algo_string`` and
``rte_cryptodev_asym_get_xform_string`` respectively.
+* eventdev: The struct rte_event_fp_ops will be updated with a new element
+ rte_eventdev_port_data to support optional callbacks in DPDK 23.11. This changes
+ the size of rte_event_fp_ops and result in ABI change.
+
* flow_classify: The flow_classify library and example have no maintainer.
The library is experimental and, as such, it could be removed from DPDK.
Its removal has been postponed to let potential users report interest
--
2.34.1
next reply other threads:[~2023-07-12 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 17:30 Sivaprasad Tummala [this message]
2023-07-13 8:51 ` Jerin Jacob
2023-07-13 10:38 ` Tummala, Sivaprasad
2023-07-13 10:40 ` Jerin Jacob
2023-07-14 11:32 ` Tummala, Sivaprasad
2023-07-17 11:24 ` [PATCH v1] " Sivaprasad Tummala
2023-07-17 11:43 ` Jerin Jacob
2023-07-17 12:42 ` Ferruh Yigit
2023-07-25 8:40 ` Ferruh Yigit
2023-07-25 16:46 ` Hemant Agrawal
2023-07-25 18:44 ` Pavan Nikhilesh Bhagavatula
2023-07-28 15:42 ` 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=20230712173050.599482-1-sivaprasad.tummala@amd.com \
--to=sivaprasad.tummala@amd.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=thomas@monjalon.net \
/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).