Re: [PATCH v5 00/10] support reinit flow

[Stephen Hemminger <stephen@networkplumber.org>]

On Thu, 17 Aug 2023 00:28:11 -0400
okaya@kernel.org wrote:

> From: Sinan Kaya <okaya@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.
> 
> Limitations:
> 
> This sequence could only be done by main lcore, and never ever in a signal handler.
> Do not try and trap signals like abort, bus error, illegal instruction and try to
> use this for recovery. It is a recipe for failure.
> 

This patch series suffers bit rot and does not apply anymore. Needs to be rebase
and resubmit.

There probably needs to be more unit-tests for restart.
Also some documentation for example, for which NIC's does this work?
Probably not all.