[dpdk-dev] [PATCH] eal: add rte_exit() main lcore limitation description
Stephen Hemminger
stephen at networkplumber.org
Fri Jun 30 05:37:20 CEST 2023
On Wed, 14 Jul 2021 17:13:00 +0300
Suanming Mou <suanmingm at nvidia.com> wrote:
> Currently, rte_eal_mp_wait_lcore() function will be called by rte_exit()
> as the routine below:
> rte_exit() -> rte_eal_cleanup() -> rte_service_finalize() ->
> rte_eal_mp_wait_lcore()
>
> As rte_eal_mp_wait_lcore() is announced can only be called from main lcore,
> rte_exit() gets the limitation implicitly as well. Or once rte_exit() is
> called from a worker core, the rte_exit() procedure will get stuck in the
> rte_eal_mp_wait_lcore() function as the core status is still running.
>
> This commit adds the limitation to rte_exit() to make things clear.
>
> Signed-off-by: Suanming Mou <suanmingm at nvidia.com>
This patch has had no response in almost two years.
The root cause of the problem is a the assumption in the service library.
That is a bug and should be filed against rte_service, not by having a
caveat in documentation that no one will read anyway.
More information about the dev
mailing list