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 51347A0569; Thu, 12 Mar 2020 04:31:32 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id C1FD11BF94; Thu, 12 Mar 2020 04:31:31 +0100 (CET) Received: from mail-il1-f195.google.com (mail-il1-f195.google.com [209.85.166.195]) by dpdk.org (Postfix) with ESMTP id AA21C2BAA for ; Thu, 12 Mar 2020 04:31:30 +0100 (CET) Received: by mail-il1-f195.google.com with SMTP id h3so4162421ils.3 for ; Wed, 11 Mar 2020 20:31:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0iTL5X5zrVDyEGp+HqFLlmsw+D6e+DzsKadd4PNkKK8=; b=I8K3A3vJ8XFI58wZP0wjF7DoEwvP2WsLnzRLhCEn3PYmFyChQMH9BE84rTGsHPIYqe iOGw8+XGD6ZOZqZl+56SEN5zRhmuNJlI5xVp1UmXe8SCMsmYTP82XK9KO1k84Nsh26du laugN6Pq13ttqHoZeoYWhbyTVx3RSAblry6Yo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0iTL5X5zrVDyEGp+HqFLlmsw+D6e+DzsKadd4PNkKK8=; b=LMXpRxBWuJ78QvuzwCUS8+1NDxK7LliFaVl+ZNqB83okWv5bJND7+VuejrgL2ayu5Z xyUZOndz9DmaZd8NnrB3RfA6lPxz5EO/q0iqUXKGa6x79SS9/XxwAFWVDvJQImDzGZar YJjRVil5u/9+8MmtJNT/FC3Qex+slapqpU8F9UfAe/zw752WorhamDqdGtl802fo5aUw YSVUeAhyogV4S76HyHGZ6xZ/8JJSzWmH0bnKegJMle5FXnZLrULkzkC8CPNK8g4K+HfI UkIfkFCrIbv8W1KRj3geqDMBgGL6YQ0zmOI8SSsA8/3lDdxGVWRmkevO8g3uYZzrdyGr WSgQ== X-Gm-Message-State: ANhLgQ2d9xk0lmc5Drys5uP2rsn23ucF3w7fKkdXl5eMavkNWDi96dyl kLXfcyX4k2zNJ+ZbNHpsT8hdsdjk4SDeQ6xIpg7eJg== X-Google-Smtp-Source: ADFU+vvk39bUs1zhVhrPlaz9PXLJXgOy3hH6DJX0mlC9GcgI423/FQBMPJZbBcxhVLTwmHu6VVYglhjgs2ri9qVJzb0= X-Received: by 2002:a92:7eda:: with SMTP id q87mr5975992ill.179.1583983889834; Wed, 11 Mar 2020 20:31:29 -0700 (PDT) MIME-Version: 1.0 References: <20200122101654.20824-1-kalesh-anakkur.purayil@broadcom.com> <20200122101654.20824-2-kalesh-anakkur.purayil@broadcom.com> <1956572.bB369e8A3T@xps> In-Reply-To: <1956572.bB369e8A3T@xps> From: Kalesh Anakkur Purayil Date: Thu, 12 Mar 2020 09:01:18 +0530 Message-ID: To: Thomas Monjalon Cc: dev@dpdk.org, ferruh.yigit@intel.com, declan.doherty@intel.com, arybchenko@solarflare.com Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] [RFC PATCH 1/3] librte_ethdev: support device recovery event 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" Hi Thomas, On Wed, Mar 11, 2020 at 6:50 PM Thomas Monjalon wrote: > 22/01/2020 11:16, Kalesh A P: > > From: Kalesh AP > > > > Adding support for recovery event in rte_eth_event framework. > > FW error and FW reset conditions would be managed by PMD. > > In such cases, PMD would need recovery events to notify application > > about PMD has recovered from FW reset or FW error. > > > > Signed-off-by: Kalesh AP > > Signed-off-by: Ajit Khaparde > > Reviewed-by: Somnath Kotur > > --- > > --- a/lib/librte_ethdev/rte_ethdev.h > > +++ b/lib/librte_ethdev/rte_ethdev.h > > @@ -3015,6 +3015,7 @@ enum rte_eth_event_type { > > RTE_ETH_EVENT_NEW, /**< port is probed */ > > RTE_ETH_EVENT_DESTROY, /**< port is released */ > > RTE_ETH_EVENT_IPSEC, /**< IPsec offload related event */ > > + RTE_ETH_EVENT_RECOVERED, /**< port recovered from an error */ > > What the application is supposed to do when receiving such event? > [Kalesh]: RTE_ETH_EVENT_RECOVERED event is an indication to the application that PMD has recovered from the reset and is functional again(i.e control path and data path is up again). On receiving this event from PMD, application has to re-create any flow rules created prior to the reset. -- Regards, Kalesh A P