From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Conole Subject: Re: [PATCH v4 00/26] linux/eal: Remove most causes of panic on init Date: Mon, 27 Feb 2017 09:34:00 -0500 Message-ID: References: <20170209142953.8167-1-aconole@redhat.com> <20170225160309.31270-1-aconole@redhat.com> <20170227135947.GB133112@bricha3-MOBL3.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain Cc: dev@dpdk.org, Stephen Hemminger To: Bruce Richardson Return-path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 588B18DA2 for ; Mon, 27 Feb 2017 15:34:01 +0100 (CET) In-Reply-To: <20170227135947.GB133112@bricha3-MOBL3.ger.corp.intel.com> (Bruce Richardson's message of "Mon, 27 Feb 2017 13:59:48 +0000") List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Bruce Richardson writes: > On Sat, Feb 25, 2017 at 11:02:43AM -0500, 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). >> > Spotted a few issues when I tried applying each of the patches and > compile testing them; those I've flagged on the patches that I test > applied. Otherwise, this looks a great set to have. > > I assume the equivalent changes to the BSD EAL are "left as an exercise > for the reader"? :-) For now. In my copious free time, I might have a crack at it, although I don't have a working BSD DPDK setup. > /Bruce