Re: [dpdk-dev] [PATCH v4 02/26] eal: return error instead of panic for cpu init

2017-02-27 Thread Aaron Conole
Bruce Richardson writes: > On Sat, Feb 25, 2017 at 11:02:45AM -0500, Aaron Conole wrote: >> There may be no way to gracefully recover, but the application >> should be notified that a failure happened, rather than completely >> aborting. This allows the user to proceed with a "slow-path" type >>

Re: [dpdk-dev] [PATCH v4 02/26] eal: return error instead of panic for cpu init

2017-02-27 Thread Aaron Conole
Bruce Richardson writes: > On Sat, Feb 25, 2017 at 11:02:45AM -0500, Aaron Conole wrote: >> There may be no way to gracefully recover, but the application >> should be notified that a failure happened, rather than completely >> aborting. This allows the user to proceed with a "slow-path" type >>

Re: [dpdk-dev] [PATCH v4 02/26] eal: return error instead of panic for cpu init

2017-02-27 Thread Bruce Richardson
On Sat, Feb 25, 2017 at 11:02:45AM -0500, Aaron Conole wrote: > There may be no way to gracefully recover, but the application > should be notified that a failure happened, rather than completely > aborting. This allows the user to proceed with a "slow-path" type > solution. > > Signed-off-by: Aa

Re: [dpdk-dev] [PATCH v4 02/26] eal: return error instead of panic for cpu init

2017-02-27 Thread Bruce Richardson
On Sat, Feb 25, 2017 at 11:02:45AM -0500, Aaron Conole wrote: > There may be no way to gracefully recover, but the application > should be notified that a failure happened, rather than completely > aborting. This allows the user to proceed with a "slow-path" type > solution. > > Signed-off-by: Aa

[dpdk-dev] [PATCH v4 02/26] eal: return error instead of panic for cpu init

2017-02-25 Thread Aaron Conole
There may be no way to gracefully recover, but the application should be notified that a failure happened, rather than completely aborting. This allows the user to proceed with a "slow-path" type solution. Signed-off-by: Aaron Conole --- lib/librte_eal/linuxapp/eal/eal.c | 13 +++-- 1 f