From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Conole Subject: Re: [PATCH v7 00/14] eal: Remove most causes of panic on init Date: Fri, 31 Mar 2017 13:54:52 -0400 Message-ID: References: <20170322201940.24028-1-aconole@redhat.com> <20170323140431.GB8688@bricha3-MOBL3.ger.corp.intel.com> <16753267.SotxTgSKUM@xps13> Mime-Version: 1.0 Content-Type: text/plain Cc: Bruce Richardson , dev@dpdk.org, Stephen Hemminger To: Thomas Monjalon Return-path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 18DC9201 for ; Fri, 31 Mar 2017 19:54:56 +0200 (CEST) In-Reply-To: <16753267.SotxTgSKUM@xps13> (Thomas Monjalon's message of "Mon, 27 Mar 2017 16:06:01 +0200") List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Thomas Monjalon writes: > 2017-03-23 14:04, Bruce Richardson: >> On Wed, Mar 22, 2017 at 04:19:26PM -0400, Aaron Conole wrote: >> > 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). >> > >> Ran a sanity test compiling with clang on FreeBSD 11 and had a quick >> scan of the patches. All looks reasonably ok to me. Did not test on >> linux. >> >> Acked-by: Bruce Richardson > > Applied, thank you so much for this work. > > Do you plan to continue hunting rte_panic in DPDK? I don't have any concrete plans to do so, but as I see them, I'll generate patches.