From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id E27F95B36 for ; Fri, 19 Oct 2018 22:53:17 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 2719F21FF9; Fri, 19 Oct 2018 16:53:17 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 19 Oct 2018 16:53:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=4fzswvDCYN0l2ydWLJPSgj5qpJpFo/tdnkozorfRDV8=; b=iCW4t3aPjh7a p7kVkwfyhRi9c4sXto7V5yaxZi8Zc2XS94lxiaRkhbC6pCuoMRlW7+tbvVCjDMEZ M9bL8TGFtQGGcuCo0vuHNSKyLRzssk1smdeyaSdCJMikAv6cLODIs2/Wmzj8mFIy Eb0CvdntYQMn6KLiRnZIRZK3f36GeKc= 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=4fzswvDCYN0l2ydWLJPSgj5qpJpFo/tdnkozorfRD V8=; b=WDHCu/LMpaRJvDcQt268FOebEINQhVnfk1vl5/nMPuk5pNv+rylcyAZug f53nysqDa/9EBxfgQj/1SMJSHMTx1YCN5oIOkOHnZc4ruDAJjpwj9IraA5HU/LFX +FXF6t7SVG8eQLRkDpP2PHqFR7giqJDlvvgNDGF6DXphhOSMNrm2nqk6ck6Xk/V6 oZh+63O6wLWo8I1WeQDIBkEPm85Z3ZEJ2TwsWb2Ij86TADI2Xm73ObjshDEtKiqc PnQYOHCsgcxP12Jf1WS9z9j8xnGpVhVoycjXg4q3FM+ZQIOAcahGza0AgEDSHy3P jneLVhSh/1aAbGa1Usz33oEVYwJzQ== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id BCA37E49C6; Fri, 19 Oct 2018 16:53:15 -0400 (EDT) From: Thomas Monjalon To: dev@dpdk.org Cc: gaetan.rivet@6wind.com, ferruh.yigit@intel.com, arybchenko@solarflare.com, wisamm@mellanox.com, ophirmu@mellanox.com Date: Fri, 19 Oct 2018 22:53:19 +0200 Message-ID: <3515806.AfmK2v9imX@xps> In-Reply-To: <20181018001949.17443-1-thomas@monjalon.net> References: <20181018001949.17443-1-thomas@monjalon.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] devargs: fix freeing during device 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, 19 Oct 2018 20:53:18 -0000 18/10/2018 02:19, Thomas Monjalon: > After calling unplug function of a bus, the device is expected > to be freed. It is too late for getting devargs to remove. > Anyway, the buses which implement unplug are already freeing > the devargs, except the PCI bus. > So the call to rte_devargs_remove() is removed from EAL and > added in PCI. > > Fixes: 2effa126fbd8 ("devargs: simplify parameters of removal function") > > Signed-off-by: Thomas Monjalon Applied