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 1CB1AA0353 for ; Tue, 19 Nov 2019 11:40:21 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 05FA41F5; Tue, 19 Nov 2019 11:40:21 +0100 (CET) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) by dpdk.org (Postfix) with ESMTP id 770FF1F5; Tue, 19 Nov 2019 11:40:19 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id BAAE6686; Tue, 19 Nov 2019 05:40:17 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 19 Nov 2019 05:40:18 -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=U21mk9fAn6GJ2XGLWS4LcRO7ZD2dPFoQb7oXw7zDdwc=; b=WmgIi0pNtSYS OTZH7M0WpZBti0XRwUFNM/fBrZeLD+eVLX75xUDgib+MFo4eHhlintZq9s8u+/Ad FeSL+kEV7pbVxMLpbyOtzfWfAF8EDGo3lklSBIF8oNjVkIYc6Q41M5YdeJdB4jld MXocB7c0kAhavravGbhQkxbhzXLXszw= 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=U21mk9fAn6GJ2XGLWS4LcRO7ZD2dPFoQb7oXw7zDd wc=; b=PcjhAezjwvbZEV7B3YZyS7LikIAs1SBgwkqvGnqASG1v/qSVi9E+4C85M L4JQ2apF16Q0nuM9j19UDi4KhWxDDVxvUd0bTsNca/FoxgzcHr+Ac0DM1llsVNCn pFq5eJZzxeLqeRbDF+XZT2rZBV1VaOX+GK1wD49TKxGSuyWWL9ctuj1r2pj+GAUN kNvH6wks2zmAL4+ntuk1J+1iJe+Q3vL7xmh6dViFQIDPL8uGJHTIWtc4ZPlaMwjt gZp74QDK0EzVNOvZ2+0vxfCdQOvWRIjvRdqM3Q3I+2iqfdhAuQGbOVZlcr87X06q WIa5MHBKQCjHWS9LxYqiiNAtlhRsw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudegkedgudejucetufdoteggodetrfdotf 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 13C6980061; Tue, 19 Nov 2019 05:40:15 -0500 (EST) From: Thomas Monjalon To: David Marchand Cc: dev , Kevin Traynor , Luca Boccassi , dpdk stable Date: Tue, 19 Nov 2019 11:40:14 +0100 Message-ID: <2832122.p5jCZFCg2j@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-stable] Backporting rte_intr_ack X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" 14/10/2019 17:55, David Marchand: > The api rte_intr_ack that has been introduced to fix a race condition > observed with (at least) qede drivers/hw. > This is an experimental api in master but it still fixes a problem, so > I'd like to see this in stable branches. This is more a driver interface than an API. > Opinions? If it comes with a fix in a driver, I think it is worth backporting.