From: Feifei Wang <feifei.wang2@arm.com>
Cc: dev@dpdk.org, nd@arm.com, Honnappa.Nagarahalli@arm.com,
Feifei Wang <feifei.wang2@arm.com>,
Ruifeng Wang <ruifeng.wang@arm.com>
Subject: [PATCH] doc: announce ethdev operation struct changes
Date: Tue, 4 Jul 2023 16:10:06 +0800 [thread overview]
Message-ID: <20230704081006.1202932-1-feifei.wang2@arm.com> (raw)
To support mbufs recycle mode, announce the coming ABI changes
from DPDK 23.11.
Signed-off-by: Feifei Wang <feifei.wang2@arm.com>
Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.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 66431789b0..c7e1ffafb2 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -118,6 +118,10 @@ Deprecation Notices
The legacy actions should be removed
once ``MODIFY_FIELD`` alternative is implemented in drivers.
+* ethdev: The Ethernet device data structure ``struct rte_eth_dev`` and
+ the fast-path ethdev flat array ``struct rte_eth_fp_ops`` will be updated
+ with new fields to support mbufs recycle mode from DPDK 23.11.
+
* cryptodev: The function ``rte_cryptodev_cb_fn`` will be updated
to have another parameter ``qp_id`` to return the queue pair ID
which got error interrupt to the application,
--
2.25.1
next reply other threads:[~2023-07-04 8:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 8:10 Feifei Wang [this message]
2023-07-04 8:17 ` Feifei Wang
2023-07-13 2:37 ` Feifei Wang
2023-07-13 12:50 ` Morten Brørup
2023-07-17 8:28 ` Andrew Rybchenko
2023-07-05 11:32 ` Konstantin Ananyev
2023-07-13 7:52 ` Ferruh Yigit
2023-07-28 14:56 ` Thomas Monjalon
2023-07-28 15:04 ` Thomas Monjalon
2023-07-28 15:08 ` Morten Brørup
2023-07-28 15:20 ` Thomas Monjalon
2023-07-28 15:33 ` Morten Brørup
2023-07-28 15:37 ` Thomas Monjalon
2023-07-28 15:55 ` Morten Brørup
2023-08-01 3:19 ` Feifei Wang
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=20230704081006.1202932-1-feifei.wang2@arm.com \
--to=feifei.wang2@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=ruifeng.wang@arm.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).