From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id C32871023 for ; Wed, 25 Jan 2017 22:33:42 +0100 (CET) Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C54D0C04B92A; Wed, 25 Jan 2017 21:33:42 +0000 (UTC) Received: from dhcp-25-97.bos.redhat.com (dhcp-25-172.bos.redhat.com [10.18.25.172]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id v0PLXf1p000838 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 25 Jan 2017 16:33:42 -0500 From: Aaron Conole To: Thomas Monjalon Cc: dev@dpdk.org References: <1483111580-5397-1-git-send-email-aconole@redhat.com> <1909688.GKiQWP6byZ@xps13> Date: Wed, 25 Jan 2017 16:33:41 -0500 In-Reply-To: <1909688.GKiQWP6byZ@xps13> (Thomas Monjalon's message of "Mon, 02 Jan 2017 15:22:40 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Wed, 25 Jan 2017 21:33:42 +0000 (UTC) Subject: Re: [dpdk-dev] [RFC 00/23] Refactor eal_init to remove panic() calls X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 21:33:43 -0000 Thomas Monjalon writes: > Hi Aaron, > > 2016-12-30 10:25, Aaron Conole: >> 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). >> >> There is still some work left in this series. > > Thanks for starting the work. > I think it is candidate for 17.05 and can be promoted in the roadmap: > http://dpdk.org/dev/roadmap > > Have you checked wether these changes are modifying the API? Looks like no API changes occur with this series. > Some doxygen comments may need to be updated when a new error code > is used. I haven't seen any instances, but if you'd like I can add that to the series as some of the error values for rte_eal_init(). -Aaron