From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 55E821B35C for ; Fri, 22 Dec 2017 09:39:12 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id CC57D20CEF; Fri, 22 Dec 2017 03:39:10 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 22 Dec 2017 03:39:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=lAlIcpxcDqte2YHIyB9ENmQEUg KYvFt9AOvc4VM5YuE=; b=OQfqfBJPExBG9Z5KaO//OaS5mcvEcrtyEPKMgYlBUC pNZgojQY0mlMsjyaPcbNvt05KgE6CeiO6q/If5NLiI4Jzy3Qhdns8SevsCovwF7m 9uOWCBAC3uxqfs1DizXsVbDzVYn2tIvIUg2IpvhGjnnbyu6e4xjfZ2AJ+jcvTEaP U= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=lAlIcp xcDqte2YHIyB9ENmQEUgKYvFt9AOvc4VM5YuE=; b=JetvqdcQnVR67L2Q3ecQ9X r8tUjJIihCAFVmOE0L3URHtI4fTOjiMesZxZ9uUwMUpPuNufHdWoeG6qD0SZuDce B2IdiKC+GZy/hzwGO+FPppe2G36XvUUN1DIIQNcJWYAdEWKxUerapo16k2wfp3JE kL0Iw7dTt3s1bKBW0a1k+VrKwQcVy7YEqQmXjspmGb7mh0U936F1QAv70n2h/MHp ldKfjA3B/XEcflUky04uOELH/3E57MaH9D3ptLMEGw3JT5yyPahSYWWbNogJ4hrp HXHcyboo+PgxLbc5LU3kBmFjJ/SNnG9NAFNI56plO88d1YFXQmdL3n6c26ADmdQQ == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 7C2777E263; Fri, 22 Dec 2017 03:39:10 -0500 (EST) From: Thomas Monjalon To: Ferruh Yigit Cc: dev@dpdk.org, matan@mellanox.com Date: Fri, 22 Dec 2017 09:39:06 +0100 Message-ID: <2461676.zTbRWfdldq@xps> In-Reply-To: <81010f97-d7fa-66da-1c8b-c4b9df0d32c9@intel.com> References: <20171128221302.15400-1-thomas@monjalon.net> <81010f97-d7fa-66da-1c8b-c4b9df0d32c9@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 08:39:12 -0000 22/12/2017 04:17, Ferruh Yigit: > 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? It can be used with port ownership, but they are two separate things.