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 8CE0EA056E; Wed, 11 Mar 2020 14:19:59 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id E12F61BF94; Wed, 11 Mar 2020 14:19:58 +0100 (CET) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id B979B3B5 for ; Wed, 11 Mar 2020 14:19:57 +0100 (CET) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id F1EFE2248B; Wed, 11 Mar 2020 09:19:56 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 11 Mar 2020 09:19:56 -0400 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=7PWYM3k7TEeAJkF2s6d2c0bhkZwm4k+WzSRSncOCwno=; b=nsaeIK7Wj3VV B5EemrBNQxKxNNTZAcxO5lP003qUJqrlYgk1kP0QdUlTEP0Mc2OgRi0/g5tPwlJN b2QPCaLE0sVELmIA6bX3VcpRakTEogdQwnUaITuRC7VQ08RJvtjvJoBXiPBNRifY zHN8/8RmkZiFIrEOGNB6QnD87HPoz7c= 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=fm2; bh=7PWYM3k7TEeAJkF2s6d2c0bhkZwm4k+WzSRSncOCw no=; b=hLJ3/GPTEv48qkVGA8HGLSVC0fv1fKvOrmoiv7i/L/1Cwin+z85jN3jbj nZyiBmEGiYj/UFQestqdwRSeswpoWxbFbKhMOltLYGWO3E8pBARgGoqfvPDl/gSj my/utKCYaIO7B+CSx7+i5kTYj27hExD64MpXD+laRNzfkEIn7TvdeFlIpOjwd570 0YuIH7WYCtESgyxLsvQ4SqtrRwFIsOvxJ8xK/10Bzuvum4w2Wt8PA5uTcrIXpUps xgOT0ldszrwG0xPLLH5Wprm7MkvFI/iK+bYb33R4JSO7wIKfgFWROfHBTukyp4rN DIgh6BjNXqWZB8dBWoIhBIrsR3c6A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedruddvvddgheduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkjghfggfgtgesthfure dttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshes mhhonhhjrghlohhnrdhnvghtqeenucfkphepjeejrddufeegrddvtdefrddukeegnecuve hluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghs sehmohhnjhgrlhhonhdrnhgvth 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 993B53280065; Wed, 11 Mar 2020 09:19:55 -0400 (EDT) From: Thomas Monjalon To: Kalesh A P Cc: dev@dpdk.org, ferruh.yigit@intel.com, declan.doherty@intel.com, arybchenko@solarflare.com Date: Wed, 11 Mar 2020 14:19:53 +0100 Message-ID: <1946963.KlZ2vcFHjT@xps> In-Reply-To: <20200122101654.20824-1-kalesh-anakkur.purayil@broadcom.com> References: <20200122101654.20824-1-kalesh-anakkur.purayil@broadcom.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [RFC PATCH 0/3] librte_ethdev: error recovery support 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" 22/01/2020 11:16, Kalesh A P: > From: Kalesh AP > > This patch adds support for recovery event in rte_eth_event framework. > FW error and FW reset conditions would be managed by PMD. Driver uses "Driver"? THE driver? :) > RTE_ETH_EVENT_INTR_RESET event to notify the applications about the > FW reset or error. Which drivers doe that? > In such cases, PMD would need recovery events to > notify application about PMD has recovered from FW reset or FW error. Sorry I don't understand. You said application is notified of any error. But the PMD can recover from this error? So what is the error at the end? If the error is recovered why notifying the application?