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 5E03AA04FD; Tue, 14 Jan 2020 11:17:36 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 7F6471C1EF; Tue, 14 Jan 2020 11:17:35 +0100 (CET) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id E2F6B1C1D9 for ; Tue, 14 Jan 2020 11:17:34 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 44A4C21DFB; Tue, 14 Jan 2020 05:17:34 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 14 Jan 2020 05:17:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=RlZ9tZZ2Qu5echNSqUM00pXQNU7eiF/SWjk0KXxqCMI=; b=fEq9BM7J2lQC c35BLBVjtdtOwZHbDJCLiGhvZnYrk0iTD/S0k96aGPol4Es1XUEcBlkWJ1u4FAGa nnQpB3EI+f2AEdpaQ0JXmg4bxF4GkO2nq/OuVrsamoeBl8DWNzoKizOHXw8zi2DR j4XxrN2mmb9eYccRWl9H7No0QmpXQJE= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=RlZ9tZZ2Qu5echNSqUM00pXQNU7eiF/SWjk0KXxqC MI=; b=aJMlQEFbPraj1vZS3MtE6RQFDKsorS2LtCszRHDt8yDgo6sZqoroAyYxY GFYK/hYCBJlCY1ZIwazAg6zPFGomFrBScaNEoI2CuQaCqQtdf3PaSHhMWKU5nAgu J91+JUtiHArKkDFX8H8Dsrl6na5Vg382NFXhovYjjUeAklFL0JCZYHDMwVCGms+k yxeJQ1lBA6n6ahJvmfpsj2SC3l3YQaQ/fa20q+xYMnpk+DkErVlmD09QLsZgNW9g fH8X3RQaHXXMRyozRb699TxogGOKN4KYMJT9/vMQXBgg1aYVbVlT+vp7NEtL1ow3 FGHwlkw24QkmcNCXSXinFVoA8Fsig== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrvdejvddgudehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 0463D80060; Tue, 14 Jan 2020 05:17:32 -0500 (EST) From: Thomas Monjalon To: Jerin Jacob Cc: Sunil Kumar Kori , David Marchand , Jerin Jacob , Nithin Dabilpuram , Vamsi Attunuru , dpdk-dev , Harman Kalra Date: Tue, 14 Jan 2020 11:17:31 +0100 Message-ID: <3698941.2iPT33SAM4@xps> In-Reply-To: References: <20191218070721.16768-2-skori@marvell.com> <20191220065645.22858-2-skori@marvell.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v6 2/2] common/octeontx2: add polling based response mbox message 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" 14/01/2020 09:41, Jerin Jacob: > On Fri, Dec 20, 2019 at 12:27 PM Sunil Kumar Kori wrote: > > > > Currently otx2_mbox_get_rsp_xxx get response once AF driver > > interrupts after completion. But this funciton will get into > > s/funciton/function > > > deadlock if called in another interrupt context. > > > > To avoid it, implemented another version of this function which polls > > on dedicated memory for a given timeout. > > > > Also after clearing interrupt, there could UP messages available for > > processing. So irq handler must check mbox messages. > > > > Signed-off-by: Sunil Kumar Kori > > Signed-off-by: Harman Kalra > > With the above change: > Acked-by: Jerin Jacob > > @Thomas Monjalon Since this patch has a dependency on an eal > patch(1/2 eal: add API to check if its interrupt context), I am > delegating this patch to EAL maintainer. Yes, we don't split series. So if there is an EAL change in a series, the whole series must be merged in master.