From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id AD5CB7CBC for ; Fri, 8 Sep 2017 11:57:01 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga105.jf.intel.com with ESMTP; 08 Sep 2017 02:57:00 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,360,1500966000"; d="scan'208";a="1216281157" Received: from irsmsx108.ger.corp.intel.com ([163.33.3.3]) by fmsmga002.fm.intel.com with ESMTP; 08 Sep 2017 02:56:59 -0700 Received: from irsmsx106.ger.corp.intel.com ([169.254.8.36]) by IRSMSX108.ger.corp.intel.com ([169.254.11.167]) with mapi id 14.03.0319.002; Fri, 8 Sep 2017 10:56:58 +0100 From: "Loftus, Ciara" To: devendra rawat , "ovs-dev@openvswitch.org" CC: "users@dpdk.org" Thread-Topic: [ovs-dev] adding dpdk ports sharing same pci address to ovs-dpdk bridge Thread-Index: AQHTJ8dN/BViPCQtLkuLr6iCINSon6KqwAww Date: Fri, 8 Sep 2017 09:56:57 +0000 Message-ID: <74F120C019F4A64C9B78E802F6AD4CC278E04762@IRSMSX106.ger.corp.intel.com> References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYjE1YjQzZmYtNjczZS00MmE1LWE5ZGQtZTJkZDM1YzEzZTVmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6ImxaQVU0RTBra0tScWpxcHJ1V2hOTGpLeFBnVGIxUmpBUmlQaEZkbkxTODQ9In0= x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] [ovs-dev] adding dpdk ports sharing same pci address to ovs-dpdk bridge X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Sep 2017 09:57:02 -0000 > Hi, >=20 > I have compiled and built ovs-dpdk using DPDK v17.08 and OVS v2.8.0. The > NIC that I am using is Mellanox ConnectX-3 Pro, which is a dual port 10G > NIC. The problem with this NIC is that it provides only one PCI address f= or > both the 10G ports. >=20 > So when I am trying to add the two DPDK ports to my br0 bridge >=20 > # ovs-vsctl --no-wait add-port br0 dpdk0 -- set Interface dpdk0 type=3Ddp= dk > options:dpdk-devargs=3D0002:01:00.0 >=20 > # ovs-vsctl --no-wait add-port br0 dpdk1 -- set Interface dpdk1 type=3Ddp= dk > options:dpdk-devargs=3D0002:01:00.0 >=20 > The port dpdk1 is added successfully and able to transfer data, but addin= g > dpdk0 to br0 fails: >=20 > 2017-09-06T14:19:20Z|00045|netdev_dpdk|INFO|Port 0: e4:1d:2d:4f:78:60 > 2017-09-06T14:19:20Z|00046|bridge|INFO|bridge br0: added interface dpdk1 > on > port 1 > 2017-09-06T14:19:20Z|00047|bridge|INFO|bridge br0: added interface br0 > on > port 65534 > 2017-09-06T14:19:20Z|00048|dpif_netlink|WARN|Generic Netlink family > 'ovs_datapath' does not exist. The Open vSwitch kernel module is probably > not loaded. > 2017-09-06T14:19:20Z|00049|netdev_dpdk|WARN|'dpdk0' is trying to use > device > '0002:01:00.0' which is already in use by 'dpdk1' > 2017-09-06T14:19:20Z|00050|netdev|WARN|dpdk0: could not set > configuration > (Address already in use) > 2017-09-06T14:19:20Z|00051|bridge|INFO|bridge br0: using datapath ID > 0000e41d2d4f7860 >=20 >=20 > With OVS v2.6.1 I never had this problem as dpdk-devargs was not > mandatory > and just specifying port name was enough to add that port to bridge. >=20 > Is there a way to add port both ports to bridge ? It seems the DPDK function rte_eth_dev_get_port_by_name() will always retur= n the port ID of the first port on your NIC, when you specify the single PC= I address and that's where the problem is. There doesn't seem to be a way c= urrently to indicate to the calling application that in fact two (or more) = port IDs are associated with the one PCI address. I am cc-ing DPDK users mailing list for hopefully some input. Are there any= plans for the rte_eth_dev_get_port_by_name function to be compatible with = NICs with multiple ports under the same PCI address? Thanks, Ciara >=20 > Thanks, > Devendra > _______________________________________________ > dev mailing list > dev@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-dev