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: announce deprecation of RTE_CPUFLAG_NUMFLAGS
Date: Wed, 12 Jul 2023 03:18:42 -0700 [thread overview]
Message-ID: <20230712101842.595809-1-sivaprasad.tummala@amd.com> (raw)
To allow new cpu features to be added without ABI breakage,
RTE_CPUFLAG_NUMFLAGS will be removed in DPDK 23.11 release.
Signed-off-by: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
---
doc/guides/rel_notes/deprecation.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 8e1cdd677a..92db59d9c2 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -28,6 +28,9 @@ Deprecation Notices
the replacement API rte_thread_set_name and rte_thread_create_control being
marked as stable, and planned to be removed by the 23.11 release.
+* eal: RTE_CPUFLAG_NUMFLAGS will be removed in DPDK 23.11 release. This is
+ to allow new cpu features to be added without ABI breakage.
+
* rte_atomicNN_xxx: These APIs do not take memory order parameter. This does
not allow for writing optimized code for all the CPU architectures supported
in DPDK. DPDK has adopted the atomic operations from
--
2.34.1
next reply other threads:[~2023-07-12 10:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 10:18 Sivaprasad Tummala [this message]
2023-07-12 10:21 ` Ferruh Yigit
2023-07-12 14:51 ` Hemant Agrawal
2023-07-25 8:39 ` Ferruh Yigit
2023-07-25 8:40 ` Bruce Richardson
2023-07-25 9:24 ` Morten Brørup
2023-07-25 9:36 ` Kevin Traynor
2023-07-25 14:18 ` Tyler Retzlaff
2023-07-25 14:24 ` Jerin Jacob
2023-07-25 16:45 ` Hemant Agrawal
2023-07-28 10:11 ` 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=20230712101842.595809-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).