From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Montorsi, Francesco" Subject: rte_eal_init() alternative? Date: Wed, 2 Sep 2015 12:49:40 +0000 Message-ID: <44e664970fef4bff942eaee5c7eaca67@bilemail1.empirix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable To: "dev@dpdk.org" Return-path: Received: from bilemail2.empirix.com (bilemail2.empirix.com [208.67.76.246]) by dpdk.org (Postfix) with ESMTP id 0D9BC688E for ; Wed, 2 Sep 2015 14:50:02 +0200 (CEST) Content-Language: en-US List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi all, Currently it seems that the only way to initialize EAL is using rte_eal_ini= t() function, correct? I have the problem that rte_eal_init() will call rte_panic() whenever somet= hing fails to initialize or in other cases it will call exit(). In my application, I would rather like to attempt DPDK initialization. If i= t fails I don't want to exit. Unfortunately I cannot even copy&paste the rte_eal_init() code into my appl= ication (removing rte_panic and exit calls) since it uses a lot of DPDK int= ernal private functions. I think that my requirements (avoid abort/exit calls when init fails) is a = basic requirement... would you accept a patch that adds an alternative rte_= eal_init() function that just returns an error code upon failure, instead o= f immediately exiting? Thanks for your hard work! Francesco Montorsi