[dpdk-dev] [RFC 02/23] eal: return error instead of panic for cpu init
Aaron Conole
aconole at redhat.com
Fri Dec 30 16:25:59 CET 2016
There may be a way to gracefully recover; at least the application
should be notified that a failure happened, rather than completely
aborting.
Signed-off-by: Aaron Conole <aconole at redhat.com>
---
lib/librte_eal/linuxapp/eal/eal.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/lib/librte_eal/linuxapp/eal/eal.c b/lib/librte_eal/linuxapp/eal/eal.c
index 16dd5b9..330f416 100644
--- a/lib/librte_eal/linuxapp/eal/eal.c
+++ b/lib/librte_eal/linuxapp/eal/eal.c
@@ -766,8 +766,11 @@ rte_eal_init(int argc, char **argv)
/* set log level as early as possible */
rte_set_log_level(internal_config.log_level);
- if (rte_eal_cpu_init() < 0)
- rte_panic("Cannot detect lcores\n");
+ if (rte_eal_cpu_init() < 0) {
+ RTE_LOG (ERR, EAL, "Cannot detect lcores\n");
+ errno = ENOTSUP;
+ return -1;
+ }
fctret = eal_parse_args(argc, argv);
if (fctret < 0)
--
2.7.4
More information about the dev
mailing list