From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from e23smtp01.au.ibm.com (e23smtp01.au.ibm.com [202.81.31.143]) by dpdk.org (Postfix) with ESMTP id CC7B42E8F for ; Sun, 20 Mar 2016 07:17:52 +0100 (CET) Received: from localhost by e23smtp01.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Sun, 20 Mar 2016 16:17:50 +1000 Received: from d23dlp02.au.ibm.com (202.81.31.213) by e23smtp01.au.ibm.com (202.81.31.207) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Sun, 20 Mar 2016 16:17:48 +1000 X-IBM-Helo: d23dlp02.au.ibm.com X-IBM-MailFrom: gowrishankar.m@linux.vnet.ibm.com X-IBM-RcptTo: users@dpdk.org Received: from d23relay08.au.ibm.com (d23relay08.au.ibm.com [9.185.71.33]) by d23dlp02.au.ibm.com (Postfix) with ESMTP id 9E1DD2BB0054 for ; Sun, 20 Mar 2016 17:17:47 +1100 (EST) Received: from d23av03.au.ibm.com (d23av03.au.ibm.com [9.190.234.97]) by d23relay08.au.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id u2K6Ha4i57933988 for ; Sun, 20 Mar 2016 17:17:47 +1100 Received: from d23av03.au.ibm.com (localhost [127.0.0.1]) by d23av03.au.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id u2K6HCKx008290 for ; Sun, 20 Mar 2016 17:17:12 +1100 Received: from [9.79.183.13] ([9.79.183.13]) by d23av03.au.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id u2K6H9NK008114; Sun, 20 Mar 2016 17:17:10 +1100 Message-ID: <56EE4053.9060306@linux.vnet.ibm.com> Date: Sun, 20 Mar 2016 11:46:51 +0530 From: gowrishankar User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Cliff Burdick CC: users@dpdk.org References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16032006-1618-0000-0000-0000450503AF Subject: Re: [dpdk-users] Difficulty With rte_eal_init() X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Mar 2016 06:17:53 -0000 Trying CONFIG_RTE_BUILD_SHARED_LIB=y and calling eal_plugin_add() for your dpdk driver .so could solve this ?. Regards, Gowrishankar On Saturday 19 March 2016 03:15 AM, Cliff Burdick wrote: > Hi, I've been trying to create a standalone application linked against > DPDK, and I'm having some issues getting the program to run properly. The > main problem is that in my standalone app compared to the example code, > rte_eal_init() from the example code seems to probe the PCI bus, whereas > mine doesn't. Here is a snippet from mine and an example: > > mine: > EAL: Virtual area found at 0x7f93ad000000 (size = 0x200000) > EAL: Ask a virtual area of 0x3fc00000 bytes > EAL: Virtual area found at 0x7f936d200000 (size = 0x3fc00000) > EAL: Ask a virtual area of 0x200000 bytes > EAL: Virtual area found at 0x7f936ce00000 (size = 0x200000) > EAL: Requesting 512 pages of size 2MB from socket 0 > EAL: Requesting 512 pages of size 2MB from socket 1 > EAL: TSC frequency is ~2500000 KHz > EAL: Master lcore 0 is ready (tid=ef4e6940;cpuset=[0]) > EAL: lcore 6 is ready (tid=699ed700;cpuset=[6]) > EAL: lcore 7 is ready (tid=691ec700;cpuset=[7]) > EAL: lcore 4 is ready (tid=6a9ef700;cpuset=[4]) > EAL: lcore 1 is ready (tid=6c1f2700;cpuset=[1]) > EAL: lcore 2 is ready (tid=6b9f1700;cpuset=[2]) > EAL: lcore 3 is ready (tid=6b1f0700;cpuset=[3]) > EAL: lcore 5 is ready (tid=6a1ee700;cpuset=[5]) > > example: > EAL: Requesting 512 pages of size 2MB from socket 1 > EAL: TSC frequency is ~2500000 KHz > EAL: Master lcore 0 is ready (tid=3019a900;cpuset=[0]) > EAL: lcore 6 is ready (tid=aabed700;cpuset=[6]) > EAL: lcore 5 is ready (tid=ab3ee700;cpuset=[5]) > EAL: lcore 7 is ready (tid=aa3ec700;cpuset=[7]) > EAL: lcore 1 is ready (tid=ad3f2700;cpuset=[1]) > EAL: lcore 3 is ready (tid=ac3f0700;cpuset=[3]) > EAL: lcore 2 is ready (tid=acbf1700;cpuset=[2]) > EAL: lcore 4 is ready (tid=abbef700;cpuset=[4]) > EAL: PCI device 0000:04:00.0 on NUMA socket 0 > EAL: probe driver: 8086:1572 rte_i40e_pmd > EAL: Not managed by a supported kernel driver, skipped > EAL: PCI device 0000:04:00.1 on NUMA socket 0 > EAL: probe driver: 8086:1572 rte_i40e_pmd > EAL: Not managed by a supported kernel driver, skipped > EAL: PCI device 0000:04:00.2 on NUMA socket 0 > ... > > I even went so far as to port the dpdk part of my C++ code to C, then > compile it into a standalone executable with the Makefile copied from an > example. Sure enough, this worked and the PCI bus was scanned. However, > when I then tried compiling the dpdk part of my app into a library and > linking against it from my main program, the PCI scanning goes away and no > devices are found. I can't really use the DPDK makefiles easily for my > entire program since I'm using automake. Has anyone had this issue? >