From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v8 22/25] eal/pci: inherit rte_driver by rte_pci_driver Date: Tue, 30 Aug 2016 16:47:37 +0100 Message-ID: <57C5AA99.7030005@intel.com> References: <1466510566-9240-1-git-send-email-shreyansh.jain@nxp.com> <1472219823-29486-1-git-send-email-shreyansh.jain@nxp.com> <1472219823-29486-23-git-send-email-shreyansh.jain@nxp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: viktorin@rehivetech.com, david.marchand@6wind.com, thomas.monjalon@6wind.com, hemant.agrawal@nxp.com To: Shreyansh Jain , dev@dpdk.org Return-path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 519BE3990 for ; Tue, 30 Aug 2016 17:47:41 +0200 (CEST) In-Reply-To: <1472219823-29486-23-git-send-email-shreyansh.jain@nxp.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 8/26/2016 2:57 PM, Shreyansh Jain wrote: > Remove the 'name' member from rte_pci_driver and move to generic rte_driver. > > Most of the PMD drivers were initially using DRIVER_REGISTER_PCI(..) > as well as assigning a name to eth_driver.pci_drv.name member. > In this patch, only the original DRIVER_REGISTER_PCI(..) name has been > populated into the rte_driver.name member - assignments through eth_driver > has been removed. > > Signed-off-by: Jan Viktorin > Signed-off-by: Shreyansh Jain > --- There are a few name fields: 1) eth_dev->data->name 2) eth_dev->data->drv_name 3) rte_driver->name 4) dev_info->driver_name What should be the relation between them? I guess 1) is device_name, 2, 3, 4 are same thing and driver_name. If this is correct, virtual drivers needs to be updated for this, because for them 3 != (2 == 4). They all use global variable for 2 & 4. And what do you think removing 2) completely? I guess it exists for virtual devices, since for them eth_driver is not exists and not able to access to rte_driver->name from eth_dev, but this is solvable. Thanks, ferruh