Bruce Richardson [off-list ref] writes:
On Sat, Feb 25, 2017 at 11:02:43AM -0500, Aaron Conole 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).
Spotted a few issues when I tried applying each of the patches and
compile testing them; those I've flagged on the patches that I test
applied. Otherwise, this looks a great set to have.
I assume the equivalent changes to the BSD EAL are "left as an exercise
for the reader"? :-)
For now. In my copious free time, I might have a crack at it, although
I don't have a working BSD DPDK setup.
/Bruce