From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.0 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2A52CC4727E for ; Wed, 30 Sep 2020 12:15:53 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id A360C206B7 for ; Wed, 30 Sep 2020 12:15:52 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org A360C206B7 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 18D461D447; Wed, 30 Sep 2020 14:15:50 +0200 (CEST) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id E38BE1D41F for ; Wed, 30 Sep 2020 14:15:46 +0200 (CEST) IronPort-SDR: YpdZvycby2j29/wec3U/nORc8iIsOCA9Nby+OAjaOQnQ7MkDW/diG4MBWLDia9WvKjBmEr95lU lzjLTCDBDnKg== X-IronPort-AV: E=McAfee;i="6000,8403,9759"; a="162489696" X-IronPort-AV: E=Sophos;i="5.77,322,1596524400"; d="scan'208";a="162489696" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 30 Sep 2020 05:15:44 -0700 IronPort-SDR: mQLRPHSM4bHiZ7tSEioaCishjleNCobWd24z8mRVIBpmHibd28bX9uP5+Ko8Q1DMMitNofZP3o 29ECjCTq6uCg== X-IronPort-AV: E=Sophos;i="5.77,322,1596524400"; d="scan'208";a="497276958" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.213.251.186]) ([10.213.251.186]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 30 Sep 2020 05:15:43 -0700 To: Thomas Monjalon , dev@dpdk.org Cc: arybchenko@solarflare.com, Wenzhuo Lu , Beilei Xing , Bernard Iremonger References: <20200913220711.3768597-1-thomas@monjalon.net> <20200928231437.414489-1-thomas@monjalon.net> <20200928231437.414489-26-thomas@monjalon.net> From: Ferruh Yigit Message-ID: <4ca79ef7-19e2-a804-0447-c25ad8375098@intel.com> Date: Wed, 30 Sep 2020 13:15:42 +0100 MIME-Version: 1.0 In-Reply-To: <20200928231437.414489-26-thomas@monjalon.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v3 25/29] app/testpmd: reset port status on close notification 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 9/29/2020 12:14 AM, Thomas Monjalon wrote: > Since rte_eth_dev_release_port() is called on all port close operations, > the event RTE_ETH_EVENT_DESTROY can be reliably used for resetting > the port status on the application side. > > The intermediate state RTE_PORT_HANDLING is removed in close_port() > because a port can also be closed by a PMD in a device remove operation. > > In case multiple ports are closed, calling remove_invalid_ports() > only once is enough. > > Signed-off-by: Thomas Monjalon > Reviewed-by: Ferruh Yigit