[PATCH v3 0/7] support reinit flow
okaya at kernel.org
okaya at kernel.org
Tue Aug 15 05:52:32 CEST 2023
From: Sinan Kaya <okaya at kernel.org>
We want to be able to call rte_eal_init() and rte_eal_cleanup()
APIs back to back for maintanance reasons.
Here is a summary of the code we have seen so far:
1. some code support getting called multiple times by keeping
a static variable.
2. some code initializes once but never clean up after them and
don't have a cleanup API.
3. some code assumes that they only get called once during the
lifecycle of the process.
Most changes in this patch center around following the #1 design
principle.
Why?
It is not always ideal to reinitialize a DPDK process. Memory needs
to be reinitialized, hugetables need to warm up etc.
Changed from
v1:
Fix checkpatch warnings
v2:
rebase to most recent DPDK.
Graham Whyte (1):
eal: fixes for re-initialization issues
Sinan Kaya (6):
tailq: skip init if already initialized
eal_memzone: bail out on initialized
memseg: init once
eal_memory: skip initialization
eal_interrupts: don't reinitialize threads
eal: initialize worker threads once
lib/eal/common/eal_common_memory.c | 5 +++
lib/eal/common/eal_common_memzone.c | 7 ++++
lib/eal/common/eal_common_options.c | 7 ++++
lib/eal/common/eal_common_tailqs.c | 20 +++++----
lib/eal/common/malloc_heap.c | 7 ++++
lib/eal/linux/eal.c | 64 ++++++++++++++++-------------
lib/eal/linux/eal_interrupts.c | 7 ++++
lib/eal/linux/eal_memory.c | 12 +++++-
8 files changed, 92 insertions(+), 37 deletions(-)
--
2.25.1
More information about the dev
mailing list