From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 54E96A0351; Mon, 18 Nov 2019 11:18:43 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id BEB69271; Mon, 18 Nov 2019 11:18:42 +0100 (CET) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id A67B123D for ; Mon, 18 Nov 2019 11:18:41 +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 orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Nov 2019 02:18:40 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.68,319,1569308400"; d="scan'208";a="196085376" Received: from aburakov-mobl1.ger.corp.intel.com (HELO [10.237.220.92]) ([10.237.220.92]) by orsmga007.jf.intel.com with ESMTP; 18 Nov 2019 02:18:39 -0800 To: Harman Kalra , Bruce Richardson Cc: "dev@dpdk.org" References: <1574019355-27695-1-git-send-email-hkalra@marvell.com> From: "Burakov, Anatoly" Message-ID: <786783c2-e9aa-6f0a-8911-3a06133c3fc6@intel.com> Date: Mon, 18 Nov 2019 10:18:38 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <1574019355-27695-1-git-send-email-hkalra@marvell.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] eal: check for interrupt context 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 17-Nov-19 7:36 PM, Harman Kalra wrote: > Added an API to check if current execution is in interrupt > context. This will be helpful to handle nested interrupt cases. > > Signed-off-by: Harman Kalra > --- This is a great idea. It would be nice to add checks for is_intr() inside rte_malloc routines, as currently attempting to rte_malloc (or allocate anything) may lead to a deadlock. Is this intended for this release, or future one? -- Thanks, Anatoly