[dpdk-dev] [RFC 00/23] Refactor eal_init to remove panic() calls

Thomas Monjalon thomas.monjalon at 6wind.com
Mon Jan 2 15:22:40 CET 2017

Hi Aaron,

2016-12-30 10:25, Aaron Conole:
> In many cases, it's enough to simply let the application know that the
> call to initialize DPDK has failed.  A complete halt can then be
> decided by the application based on error returned (and the app could
> even attempt a possible re-attempt after some corrective action by the
> user or application).
> There is still some work left in this series.

Thanks for starting the work.
I think it is candidate for 17.05 and can be promoted in the roadmap:

Have you checked wether these changes are modifying the API?
Some doxygen comments may need to be updated when a new error code
is used.

More information about the dev mailing list