From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH] ethdev: add notifications for probing and removal Date: Thu, 21 Dec 2017 19:17:04 -0800 Message-ID: <81010f97-d7fa-66da-1c8b-c4b9df0d32c9@intel.com> References: <20171128221302.15400-1-thomas@monjalon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: matan@mellanox.com To: Thomas Monjalon , dev@dpdk.org Return-path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id BF94A1B310 for ; Fri, 22 Dec 2017 04:17:05 +0100 (CET) In-Reply-To: <20171128221302.15400-1-thomas@monjalon.net> Content-Language: en-US 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 11/28/2017 2:13 PM, Thomas Monjalon wrote: > When a PMD finishes probing, it creates the new port by calling > the function rte_eth_dev_allocate(). > A notification of the new port is sent there to the upper layer. > > When a PMD finishes removal of a port, it calls the function > rte_eth_dev_release_port(). > A notification of the destroyed port is sent there to the upper layer. > > Signed-off-by: Thomas Monjalon Reviewed-by: Ferruh Yigit > --- > > This patch depends on: > - ethdev: remove useless parameter in callback process > - ethdev: free a port by a dedicated API What do you think pulling that patch from port ownership patchset, which is still under discussion, to this one? Is it required for port ownership one?