[dpdk-dev] [RFC 00/23] Refactor eal_init to remove panic() calls
aconole at redhat.com
Tue Jan 3 17:06:25 CET 2017
Thomas Monjalon <thomas.monjalon at 6wind.com> writes:
> 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?
That'll be my last pass through.
> Some doxygen comments may need to be updated when a new error code
> is used.
Agreed; I also want to ensure that there's a consistent set of error
codes, and a consistent place to check for them.
I'll probably prefer to put them in rte_errno.
Thanks for your thoughts, Thomas!
More information about the dev