From: Sinan Kaya <ok...@kernel.org> Call of rte_eal_init() api after rte_eal_cleanup() possible for certain application types but this is not an officially supported feature.
Signed-off-by: Sinan Kaya <ok...@kernel.org> --- lib/eal/include/rte_eal.h | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/lib/eal/include/rte_eal.h b/lib/eal/include/rte_eal.h index 53c4a5519e..348b340f00 100644 --- a/lib/eal/include/rte_eal.h +++ b/lib/eal/include/rte_eal.h @@ -67,6 +67,11 @@ int rte_eal_iopl_init(void); * as possible in the application's main() function. * It puts the WORKER lcores in the WAIT state. * + * @warning + * It maybe possisble to call it again after rte_eal_cleanup(). + * But this usage is dependent on libraries and drivers support which + * may not work. Use at your own risk. + * * @param argc * A non-negative value. If it is greater than 0, the array members * for argv[0] through argv[argc] (non-inclusive) shall contain pointers -- 2.25.1
