From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id E83195F34 for ; Wed, 7 Mar 2018 10:05:55 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Mar 2018 01:05:54 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,435,1515484800"; d="scan'208";a="22673307" Received: from aburakov-mobl.ger.corp.intel.com (HELO [10.252.5.25]) ([10.252.5.25]) by orsmga007.jf.intel.com with ESMTP; 07 Mar 2018 01:05:53 -0800 To: Thomas Monjalon , Arnon Warshavsky Cc: bruce.richardson@intel.com, dev@dpdk.org References: <1520360928-9375-1-git-send-email-arnon@qwilt.com> <304114136.g7uiPYdxRp@xps> From: "Burakov, Anatoly" Message-ID: Date: Wed, 7 Mar 2018 09:05:51 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <304114136.g7uiPYdxRp@xps> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] eal: register rte_panic user callback 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, 07 Mar 2018 09:05:57 -0000 On 07-Mar-18 8:32 AM, Thomas Monjalon wrote: > Hi, > > 06/03/2018 19:28, Arnon Warshavsky: >> The use case addressed here is dpdk environment init >> aborting the process due to panic, >> preventing the calling process from running its own tear-down actions. > > Thank you for working on this long standing issue. > >> A preferred, though ABI breaking solution would be >> to have the environment init always return a value >> rather than abort upon distress. > > Yes, it is the preferred solution. > We should not use exit (panic & co) inside a library. > It is important enough to break the API. +1, panic exists mostly for historical reasons AFAIK. it's a pity i didn't think of it at the time of submitting the memory hotplug RFC, because i now hit the same issue with the v1 - we might panic while holding a lock, and didn't realize that it was an API break to change this behavior. Can this really go into current release without deprecation notices? -- Thanks, Anatoly