From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] net/bonding: support bifurcated driver in eal cli using --vdev Date: Fri, 16 Jun 2017 16:34:41 +0200 Message-ID: <3047033.M7f3S2WmBF@xps> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Declan Doherty , Chao Zhu , olgas@mellanox.com, adrien.mazarguil@6wind.com, gaetan.rivet@6wind.com To: Gowrishankar Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id AE0E62BB9 for ; Fri, 16 Jun 2017 16:34:42 +0200 (CEST) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 14/06/2017 12:49, Gowrishankar: > At present, creating bonding devices using --vdev is broken for PMD like > mlx5 as it is neither UIO nor VFIO based and hence PMD driver is unknown > to find_port_id_by_pci_addr(), as below. > > testpmd --vdev 'net_bonding0,mode=1,slave=,socket_id=0' > > PMD: bond_ethdev_parse_slave_port_kvarg(150) - Invalid slave port value > () specified > EAL: Failed to parse slave ports for bonded device net_bonding0 Thanks for reporting. > This patch adds RTE_KDRV_BIFURCATED in rte_kernel_driver for the PMD > driver like mlx5 to be a known one. The current kdrv value should be RTE_KDRV_UNKNOWN for Mellanox devices. I do not see the value of creating a new type. I think the issue is in the bonding code (find_port_id_by_pci_addr): * TODO: Once the PCI bus has arrived we should have a better * way to test for being a PCI device or not. */ if (rte_eth_devices[i].data->kdrv == RTE_KDRV_UNKNOWN || rte_eth_devices[i].data->kdrv == RTE_KDRV_NONE) continue;