From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Rybchenko Subject: Re: [RFC] ethdev: complete closing to free all resources Date: Mon, 10 Sep 2018 11:54:01 +0300 Message-ID: <402147ea-d88a-27a0-25a9-905c79fb5b89@solarflare.com> References: <20180907233929.21950-1-thomas@monjalon.net> <47678eef-0260-302a-b46b-2cdf861322a6@solarflare.com> <2007089.03mgKk1tIn@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Cc: , To: Thomas Monjalon Return-path: Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [148.163.129.52]) by dpdk.org (Postfix) with ESMTP id 31E8810BD for ; Mon, 10 Sep 2018 10:54:35 +0200 (CEST) In-Reply-To: <2007089.03mgKk1tIn@xps> 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 09/10/2018 11:42 AM, Thomas Monjalon wrote: > 10/09/2018 10:03, Andrew Rybchenko: >> On 09/08/2018 02:39 AM, Thomas Monjalon wrote: >>> After closing a port, it cannot be restarted. >>> So there is no reason to not free all associated resources. >>> >>> The last step was done with rte_eth_dev_detach() which is deprecated. >>> Instead of removing the associated rte_device, the driver should check >>> if no more port (ethdev, cryptodev, etc) is still open for the device. >>> Then the device resources can be freed by the driver inside the >>> dev_close() driver callback operation. >>> >>> The last ethdev freeing (dev_private and final release), which were done >>> by rte_eth_dev_detach(), are now done at the end of rte_eth_dev_close(). >> For me, it sounds more logical to kill dev_close and keep detach. >> IMHO, dev_close is artificial and hardly useful. detach is a local pair >> to attach. > I don't get your point. > > In order to free a port, we need close + detach. > We can keep only one. > I choose close because: > 1) attach/detach are deprecated > 2) probe/close is a more obvious pair > 3) we need the driver to free the lower level resources Yes, I'm sorry I used bad terminology. We have probe/remove pair for both PCI and vdev drivers and I mean that remove is a better candidate to be kept (as a pair for probe which allocates all resources).