[dpdk-dev] [PATCH] eal: promote non-EAL lcore API as stable

[Kevin Traynor]

On 22/10/2021 07:55, David Marchand wrote:
> This API has been around for more than a year (and is in LTS 20.11).
> It did not receive negative feedback and will be used in a next OVS
> release.
> Mark it stable.
> 
> Signed-off-by: David Marchand <david.marchand at redhat.com>

I have tested with rte_lcore_dump(), rte_mp_disable(), 
rte_thread_register(), rte_thread_unregister() in OVS patches and they 
are straightforward API and worked fine. rte_lcore_iterate() tested 
implicitly through rte_lcore_dump().

I haven't used 
rte_lcore_callback_register()/rte_lcore_callback_unregister() as they 
are optional but it doesn't make sense to leave them experimental while 
promoting rte_thread_register()/rte_thread_unregister() which call those 
callbacks.

Noting that rte_lcore_iterate() is also in use for 1+ year from 
mempool_bucket.

Acked-by: Kevin Traynor <ktraynor at redhat.com>