[v6,3/3] doc: announce deprecation of thread ctrl create function
Checks
Commit Message
Notify deprecation of rte_ctrl_thread_create API, it will be removed as
it exposes platform-specific thread details.
Signed-off-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
Acked-by: Morten Brørup <mb@smartsharesystems.com>
Acked-by: David Marchand <david.marchand@redhat.com>
Reviewed-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
---
doc/guides/rel_notes/deprecation.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
Comments
On Wed, Feb 08, 2023 at 01:26:35PM -0800, Tyler Retzlaff wrote:
> Notify deprecation of rte_ctrl_thread_create API, it will be removed as
> it exposes platform-specific thread details.
>
> Signed-off-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
> Acked-by: Morten Brørup <mb@smartsharesystems.com>
> Acked-by: David Marchand <david.marchand@redhat.com>
> Reviewed-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
> ---
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
@@ -23,10 +23,10 @@ Deprecation Notices
in the future. Applications can use ``devtools/cocci/func_or_ret.cocci``
to update their code.
-* eal: The function ``rte_thread_setname`` is planned to be deprecated
- starting with the 23.07 release, subject to the replacement API
- rte_thread_set_name being marked as stable, and planned to be removed
- by the 23.11 release.
+* eal: The function ``rte_thread_setname`` and ``rte_ctrl_thread_create``
+ are planned to be deprecated starting with the 23.07 release, subject to
+ 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.
* 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