From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id AA758379E for ; Wed, 23 Dec 2015 08:28:44 +0100 (CET) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 22 Dec 2015 23:28:43 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,467,1444719600"; d="scan'208";a="877293279" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by orsmga002.jf.intel.com with ESMTP; 22 Dec 2015 23:28:43 -0800 Received: from fmsmsx113.amr.corp.intel.com (10.18.116.7) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 22 Dec 2015 23:28:43 -0800 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by FMSMSX113.amr.corp.intel.com (10.18.116.7) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 22 Dec 2015 23:28:42 -0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.158]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.92]) with mapi id 14.03.0248.002; Wed, 23 Dec 2015 15:28:40 +0800 From: "Lu, Wenzhuo" To: Vithal Mohare , "dev@dpdk.org" Thread-Topic: DPDP crash with sr-iov (with ESXi 5.5 hypervisor) Thread-Index: AdE9OFP61psgBGHvQEaH4SJQ9XSGSQAGO0Ig Date: Wed, 23 Dec 2015 07:28:40 +0000 Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC0909020D08AC@shsmsx102.ccr.corp.intel.com> References: <98DB008FA2AC6644B40AD8C766FAB271021FA1A4D4@PWSN02.arubanetworks.com> In-Reply-To: <98DB008FA2AC6644B40AD8C766FAB271021FA1A4D4@PWSN02.arubanetworks.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZGQwYjc0OWQtYjNkZi00ODE0LTk5YTMtZDkwMDJmODUzN2QwIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjQuMTAuMTkiLCJUcnVzdGVkTGFiZWxIYXNoIjoieXg5WVg1MEpsQ3ZwT1dnWGYxR3MxVWw1OXFIWkxBdXNvSWQyd09jdUtkMD0ifQ== x-ctpclassification: CTP_IC x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] DPDP crash with sr-iov (with ESXi 5.5 hypervisor) X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Dec 2015 07:28:45 -0000 Hi Vithal, The number of VF queues is decided by PF. Suppose you use kernel driver for= PF. So the queue number is decided by PF kernel driver. I have a 82599ES, and find no matter ixgbevf or dpdk igb_uio is used, the r= x queue number is 2. Frankly, I believe 2 is the expected number. Surprised= that you get 8 when using ixgbevf. Hope this can help. Thanks. > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Vithal Mohare > Sent: Wednesday, December 23, 2015 12:32 PM > To: dev@dpdk.org > Subject: [dpdk-dev] DPDP crash with sr-iov (with ESXi 5.5 hypervisor) >=20 > Hi, >=20 > While initializing pci port (VF) DPDK is crashing while configuring the d= evice. > Reason/location: > PMD: rte_eth_dev_configure: ethdev port_id=3D1 nb_rx_queu= es=3D8 > > 2 > EAL: Error - exiting with code: 1 >=20 > System info: > DPDK version: 2.0 > NIC: 82599EB, sr-iov enabled. > SR-IOV config at ESXi 5.5 hypervisor host: max_vfs=3D2 Guest OS: Linux OS > based. Driver: ixgbevf.ko >=20 > VM is configured with 3 vCPUs. Before linking the port to DPDK, I see th= at, > pci device (VF) comes up with 8 rx/tx queues (using native kernel driver > ixgbevf.ko, /sys/class/net/ethx/queues/*). But DPDK code expect max > queues for device to be '2' and hence the crash. Am I missing anything = here? > Appreciate for any suggestions/fixes for the issue. >=20 > Thanks, > -Vithal