From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from jaguar.aricent.com (jaguar.aricent.com [121.241.96.11]) by dpdk.org (Postfix) with ESMTP id A81A6156 for ; Thu, 17 Oct 2013 13:52:13 +0200 (CEST) Received: from jaguar.aricent.com (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id E079C36B69; Thu, 17 Oct 2013 17:22:42 +0530 (IST) Received: from GUREXHT02.ASIAN.AD.ARICENT.COM (gurexht02.asian.ad.aricent.com [10.203.171.138]) by jaguar.aricent.com (Postfix) with ESMTP id 7C8CD36B55; Thu, 17 Oct 2013 17:22:42 +0530 (IST) Received: from GUREXMB01.asian.ad.aricent.com ([10.203.171.134]) by GUREXHT02.ASIAN.AD.ARICENT.COM ([10.203.171.138]) with mapi; Thu, 17 Oct 2013 17:22:21 +0530 From: Prashant Upadhyaya To: jigsaw , "dev@dpdk.org" Date: Thu, 17 Oct 2013 17:22:17 +0530 Thread-Topic: [dpdk-dev] 82599 SR-IOV with passthrough Thread-Index: Ac7KafTfvFFOVeiNTsq203vy+vKzSgAw4D8Q Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-TM-AS-MML: No Subject: Re: [dpdk-dev] 82599 SR-IOV with passthrough 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: Thu, 17 Oct 2013 11:52:14 -0000 Hi Qinglai, Even with 1 queue, were you able to run the DPDK app in the guest OS ? If you were able to, which version of DPDK did you use, please let me know. I am trying to run the DPDK app in guest OS using QEMU/KVM with an SRIOV vi= rtual function of an 82599 NIC. I can see the vf pci address in the lspci output on the guest OS, but when = I try to run the DPDK app in the guest OS, the EAL complains with the follo= wing -- EAL: pci_uio_map_resource(): cannot store uio mmap details I am using DPDK1.4. Regards -Prashant -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of jigsaw Sent: Wednesday, October 16, 2013 5:49 PM To: dev@dpdk.org Subject: [dpdk-dev] 82599 SR-IOV with passthrough Hi, I am doing experiments with SR-IOV + passthrough on 82599. My expectation is to have VT on and DCB off, under which configuration, the= total 128 TX queues will be split into 32 pools, each has 4 queues. With latest driver ixgbe-3.18.7, PF can be set with 16 pools, each has 4 queues with these params: insmod ./ixgbe.ko MQ=3D1 max_vfs=3D8 RSS=3D8 VMDQ=3D16 I tried with VMDQ=3D32 with a panic. Also, it seems that if RSS is set to 4= , the PF driver will set RSS to 2 somehow. Since I'm fine with 16 pools + 4 queues, I'm not going to investigate (at = this moment) why PF doesn't work as expected. Next step is then to try DPDK in guest OS, which get one VF by passthrough. Not surprisingly, DPDK says that number of TX queue is 1. This is because t= he value is set arbitrarily in ixgbe_init_ops_vf of ixgbe_vf.c, and it neve= r gets updated. Actually the mbox API has support for requesting Tx/Rx queue numbers from V= F. See implementation of routine ixgbevf_get_queues and ixgbevf_negotiate_a= pi_version. However, it is not straightforward to use these 2 routines to fetch Tx/Rx q= ueue number, coz the PF driver is not ready to be used without modification= . See ixgbe_get_vf_queues of ixgbe_sriov.c in ixgbe-3.18.7. The PF will alwa= ys answer with 1 for Tx/Rx queue number requests, regardless of current con= fig. Therefore, to add support for multiple queues per VF, we have to at least f= ix the PF driver, then add support in DPDK's VF driver. But the question is, is this enough? Before doing any experiments I wonder = whether anybody has come across same problem as I do, and if there's any im= plementation ongoing. thx & rgds, -Qinglai =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D