Stephen Hemminger <step...@networkplumber.org> writes: > On Thu, 9 Feb 2017 09:29:28 -0500 > Aaron Conole <acon...@redhat.com> wrote: > >> 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). >> >> ... >> > > I worry that some of these early failure messages may never be visible > because the logging system has not been initialized. Might be safer to > just use fprintf(stderr, ...) or define a new wrapper function.
Thanks for the suggestion, Stephen! I've folded it into my series. -Aaron
