> It's possible for dpdk initialization to fail either due to an internal
> error or an invalid configuration. When that happens, it's rather
> impolite to immediately abort without any details.
>
> With this change, a failed dpdk initialization attempt will continue to
> trigger a SIGABRT. Howe
On 05/03/2018 08:08 PM, Aaron Conole wrote:
> It's possible for dpdk initialization to fail either due to an internal
> error or an invalid configuration. When that happens, it's rather
> impolite to immediately abort without any details.
>
> With this change, a failed dpdk initialization attempt
It's possible for dpdk initialization to fail either due to an internal
error or an invalid configuration. When that happens, it's rather
impolite to immediately abort without any details.
With this change, a failed dpdk initialization attempt will continue to
trigger a SIGABRT. However, the fai
