From mboxrd@z Thu Jan 1 00:00:00 1970 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) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Dec 2017 19:17:04 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,438,1508828400"; d="scan'208";a="4691578" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.241.224.153]) ([10.241.224.153]) by orsmga007.jf.intel.com with ESMTP; 21 Dec 2017 19:17:04 -0800 To: Thomas Monjalon , dev@dpdk.org Cc: matan@mellanox.com References: <20171128221302.15400-1-thomas@monjalon.net> From: Ferruh Yigit Message-ID: <81010f97-d7fa-66da-1c8b-c4b9df0d32c9@intel.com> Date: Thu, 21 Dec 2017 19:17:04 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <20171128221302.15400-1-thomas@monjalon.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] ethdev: add notifications for probing and removal 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: Fri, 22 Dec 2017 03:17:07 -0000 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?