Thread (159 messages) 159 messages, 4 authors, 2017-03-10

Re: [PATCH v3 00/25] linux/eal: Remove most causes of panic on init

From: Aaron Conole <aconole@redhat.com>
Date: 2017-02-14 20:50:25

Stephen Hemminger [off-list ref] writes:
On Thu,  9 Feb 2017 09:29:28 -0500
Aaron Conole [off-list ref] wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help