[PATCH v4 0/8] support reinit flow
Stephen Hemminger
stephen at networkplumber.org
Tue Aug 15 21:47:43 CEST 2023
On Tue, 15 Aug 2023 14:58:03 -0400
Sinan Kaya <okaya at kernel.org> wrote:
> >
> > As a compromise, can this restart be officially tagged as
> > unsupported.
>
> any pointers how to do this?
>
> I have no idea how to mark something unsupported in code.
> If this is acceptable in cover letter, I'm happy to do that too.
Put some additional notes in the rte_eal.h like:
diff --git a/lib/eal/include/rte_eal.h b/lib/eal/include/rte_eal.h
index 53c4a5519e61..348b340f006d 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
Or maybe in the Shutdown and Cleanup section of:
doc/guides/prog_guide/env_abstraction_layer.rst
More information about the dev
mailing list