From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by dpdk.org (Postfix) with ESMTP id 259DE378B for ; Mon, 10 Sep 2018 17:24:30 +0200 (CEST) Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 999F24021712; Mon, 10 Sep 2018 15:24:29 +0000 (UTC) Received: from ktraynor.remote.csb (ovpn-117-56.ams2.redhat.com [10.36.117.56]) by smtp.corp.redhat.com (Postfix) with ESMTP id 211C12157F49; Mon, 10 Sep 2018 15:24:27 +0000 (UTC) To: Qi Zhang , thomas@monjalon.net, declan.doherty@intel.com, ferruh.yigit@intel.com Cc: dev@dpdk.org References: <20180910140437.6741-1-qi.z.zhang@intel.com> From: Kevin Traynor Organization: Red Hat Message-ID: <28d2e815-a5aa-377f-11bd-9c80b195c368@redhat.com> Date: Mon, 10 Sep 2018 16:24:22 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <20180910140437.6741-1-qi.z.zhang@intel.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.5]); Mon, 10 Sep 2018 15:24:29 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.5]); Mon, 10 Sep 2018 15:24:29 +0000 (UTC) for IP:'10.11.54.6' DOMAIN:'int-mx06.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'ktraynor@redhat.com' RCPT:'' Subject: Re: [dpdk-dev] [PATCH] doc: update API deprecation for device reset 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: , X-List-Received-Date: Mon, 10 Sep 2018 15:24:30 -0000 On 09/10/2018 03:04 PM, Qi Zhang wrote: > Device reset may have the dependency, for example, a VF reset expects > PF ready, or a NIC function as a part of a SOC need to wait for other > parts of the system be ready, these are time-consuming tasks and will > block current thread. > > So we claimed rte_eth_dev_reset as an async API, that makes things > easy for an application that what to reset the device from the interrupt > thread since typically a RTE_ETH_EVENT_INTR_RESET handler is invoked > in interrupt thread. > I think it may be better to give the function with new async behaviour a new name. Otherwise, it could be confusing for users who are currently taking some action based on the return value from the current blocking version of the function. What do you think? > RFC patch: > http://patchwork.dpdk.org/patch/44513/ > > Signed-off-by: Qi Zhang > --- > doc/guides/rel_notes/deprecation.rst | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst > index bade1e4c4..3490aac87 100644 > --- a/doc/guides/rel_notes/deprecation.rst > +++ b/doc/guides/rel_notes/deprecation.rst > @@ -95,3 +95,8 @@ Deprecation Notices > - ``rte_pdump_set_socket_dir`` will be removed; > - The parameter, ``path``, of ``rte_pdump_init`` will be removed; > - The enum ``rte_pdump_socktype`` will be removed. > + > +* ethdev: In v19.02 ``rte_eth_dev_reset`` is claimed as an async API. > + Application should not assume device reset is finished after > + ``rte_eth_dev_reset`` return, it should always wait for a > + RTE_ETH_EVENT_RESET_COMPLETE event and check the reset result. >