From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from inblrg01.tcs.com (inblrg01.tcs.com [121.242.48.3]) by dpdk.org (Postfix) with ESMTP id 29563590B for ; Tue, 29 Apr 2014 11:28:54 +0200 (CEST) X-IronPort-AV: E=Sophos;i="4.97,950,1389724200"; d="scan'208";a="109848632" Received: from INBLRDLPMTA2.india.tcs.com (unknown [127.0.0.1]) by INBLRDLPMTA2.india.tcs.com (Service) with ESMTP id B3CF9128E12; Tue, 29 Apr 2014 14:58:55 +0530 (IST) Received: from InHydM02.tcs.com (unknown [172.25.68.72]) by INBLRDLPMTA2.india.tcs.com (Service) with ESMTP id 4C773128E02; Tue, 29 Apr 2014 14:58:55 +0530 (IST) Importance: Normal X-Priority: 3 (Normal) Sensitivity: In-Reply-To: References: <8080666.eQLb0Bv3Fe@xps13>, MIME-Version: 1.0 From: B Gopikrishna To: Tomasz K Message-ID: Date: Tue, 29 Apr 2014 14:58:52 +0530 X-Mailer: Lotus Domino Web Server Release 8.5.3FP2 July 02, 2012 X-MIMETrack: Serialize by Notes Server on InHydM02/TCS(Release 8.5.3FP2|July 02, 2012) at 04/29/2014 14:58:52, Serialize complete at 04/29/2014 14:58:52, Itemize by Notes Server on InHydM02/TCS(Release 8.5.3FP2|July 02, 2012) at 04/29/2014 14:58:52, Serialize by Notes Server on InHydM02/TCS(Release 8.5.3FP2|July 02, 2012) at 04/29/2014 14:58:54, Serialize complete at 04/29/2014 14:58:54, Serialize by Router on InHydM02/TCS(Release 8.5.3FP2|July 02, 2012) at 04/29/2014 14:58:55, Serialize complete at 04/29/2014 14:58:55 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: dev Subject: Re: [dpdk-dev] rte_eth_dev_configure fails on VM with e1000 drivers 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: Tue, 29 Apr 2014 09:28:55 -0000 Apologies for the delayed reply, we continued with 1 core to complete our w= ork. But = currently we would like to extend running the application with 2 core's and= we are still unable to after following suggestions by = Thomas, the commit mentioned by you is already available as part of the DPD= K code we compiled. = = Tomasz, we tried with the port mask of 0x06, but this doesnot work either. = Any other suggestions or pointers to resolve the same would be of great hel= p. Thankyou = Regards Gopi Krishna B -----Tomasz K wrote: ----- To: Thomas Monjalon From: Tomasz K Date: 04/18/2014 06:07PM cc: B Gopikrishna , dev Subject: Re: [dpdk-dev] rte_eth_dev_configure fails on VM with e1000 drivers Hi Gopi I recently run into the same problem when using 82576 with igb_uio on VM. The problem is not e1000 or igb. The problem is with the other network devi= ce managed by virtio-pci driver Notice that when application polls for ETH devices it prints out EAL: probe driver: 1af4:1000 rte_virtio_pmd EAL: 0000:00:03.0 not managed by UIO driver, skipping So even though this NIC is not managed by igb_uio driver the app prints tha= t driver used for it is rte_virtio_pmd. After setting up ETH devices app tries to set up tx/rx queues and it fails = on port 0 (which is virtio) You can try and run the application with -p 0x6 instead of 0x3. This should= mask out port0 from configuration Thanks Tomasz 2014-04-18 14:31 GMT+02:00 Thomas Monjalon : Hi, 2014-04-18 17:39, B Gopikrishna: > when I run the l3fwd application with the below command line, I am observ= ing > the error "Cannot configure device: err=3D-22, port=3D0". The complete lo= g is > posted below. Could you try to reproduce it with the git HEAD version? It may be fixed by this commit: d73d8f3 timer: fix TSC frequency by not reading /proc/cpuinfo -- Thomas =3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D Notice: The information contained in this e-mail message and/or attachments to it may contain = confidential or privileged information. If you are = not the intended recipient, any dissemination, use, = review, distribution, printing or copying of the = information contained in this e-mail message = and/or attachments to it are strictly prohibited. If = you have received this communication in error, = please notify us by reply e-mail or telephone and = immediately and permanently delete the message = and any attachments. Thank you