From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH 15/25] eal: do not panic on alarm init Date: Fri, 27 Jan 2017 16:42:02 +0000 Message-ID: <20170127164201.GA82692@bricha3-MOBL3.ger.corp.intel.com> References: <1485529023-5486-1-git-send-email-aconole@redhat.com> <1485529023-5486-16-git-send-email-aconole@redhat.com> <20170127083155.71fb20cb@xeon-e3> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Aaron Conole , dev@dpdk.org To: Stephen Hemminger Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 55E99FFA for ; Fri, 27 Jan 2017 17:42:05 +0100 (CET) Content-Disposition: inline In-Reply-To: <20170127083155.71fb20cb@xeon-e3> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, Jan 27, 2017 at 08:31:55AM -0800, Stephen Hemminger wrote: > On Fri, 27 Jan 2017 09:56:53 -0500 > Aaron Conole wrote: > > > + if (rte_eal_alarm_init() < 0) { > > + RTE_LOG (ERR, EAL, "Cannot init interrupt-handling thread\n"); > > + /* rte_eal_alarm_init sets rte_errno on failure. */ > > + errno = rte_errno; > > Hmm. DPDK in general does not reset errno but instead uses error code > directly on return (best) or in some cases rte_errno I think we'll disagree on what way of returning error codes is best :-), but yes, DPDK does not generally modify errno.