From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qg0-f47.google.com (mail-qg0-f47.google.com [209.85.192.47]) by dpdk.org (Postfix) with ESMTP id C6A2D5A86 for ; Fri, 16 Jan 2015 17:47:56 +0100 (CET) Received: by mail-qg0-f47.google.com with SMTP id j5so3587152qga.6 for ; Fri, 16 Jan 2015 08:47:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=zUqPppcry08w7UnThKyEGKW019rY78cjNe+Gn/PPmQg=; b=GOOGFDDgX2VncDNknV+CW94sNYXy7pMulgXMm1cNqF4RBOrkKi9YTjbvAWoiRgyzFt Zu9/y08snVvDvvrCoc8s8vt1CIu4ve9k2ekM8XjkgYQeRZzKaaqUhwxvQKPRleeOaLOX jFdDXbkir+N8ktI+FRok0TxupyTYraLdJeOsFeslcKHczvW2sZdtX8irqHSyuwDUgi+l q5oYlzk14Nh0XKifJi+Ezd++tBiIx1+VoUslyCwvnCqfy36ri7GQhgv+gQnOK46fgrCH tWEPKdqwC63UyqQM3sae7tkUEuvV5zhTdny3KAP09XKimCgeyI+iDpSPXMxekhFm5Lt8 1VZQ== MIME-Version: 1.0 X-Received: by 10.140.40.230 with SMTP id x93mr1917739qgx.46.1421426876191; Fri, 16 Jan 2015 08:47:56 -0800 (PST) Received: by 10.229.181.8 with HTTP; Fri, 16 Jan 2015 08:47:56 -0800 (PST) In-Reply-To: <54B93DCE.50607@6wind.com> References: <20141224150401.GB23653@localhost.localdomain> <20141225170848.GA3199@localhost.localdomain> <20141226143737.GB5567@localhost.localdomain> <20150110124431.GA14681@localhost.localdomain> <54B91FE3.8010607@6wind.com> <54B93DCE.50607@6wind.com> Date: Fri, 16 Jan 2015 17:47:56 +0100 Message-ID: From: sothy shan To: Olivier MATZ Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21 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: Fri, 16 Jan 2015 16:47:57 -0000 On Fri, Jan 16, 2015 at 5:35 PM, Olivier MATZ wrot= e: > Hi Sothy, > > On 01/16/2015 05:07 PM, sothy shan wrote: >> On Fri, Jan 16, 2015 at 3:27 PM, Olivier MATZ w= rote: >>>> When I do with >>>> >>>> export RTE_SDK=3D$(pwd)export RTE_TARGET=3D"x86_64-ivshmem-linuxapp-gc= c" >>>> make CONFIG_RTE_BUILD_COMBINE_LIBS=3Dy CONFIG_RTE_BUILD_SHARED_LIB=3Dy >>>> install T=3D"$RTE_TARGET" >>> >>> Are you sure that this syntax is supported by the build system? >> >> I am tryiting to build DPDK OVS and found the instruction in >> https://github.com/01org/dpdk-ovs/blob/development/docs/01_Installation.= md > > I just noticed the syntax is strange, you can check the supported > options here: > > http://dpdk.org/doc/guides/prog_guide/dev_kit_build_system.html#makefile-= description For me, I followed the top leve compilation and compilation went well. https://github.com/01org/dpdk-ovs/blob/development/docs/01_Installation.md It means those paremeters are taken into account somewhere. Now I didnt check testpmd command and directly went to run ovs-dpdk in Fedora 20 with DPDK OVS 1.2 I am in another problem. I guess it is out of your focus, I just give you the idea. =C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2= =A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3= =C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2= =A3=C2=A3=C2=A3 sudo ./datapath/dpdk/ovs-dpdk -c 0x1E -n 4 --proc -type primary --huge-dir=3D/mnt/huge -- --stats_core=3D4 --stats=3D5 -p 0x07 EAL: Detected lcore 0 as core 0 on socket 0 EAL: Detected lcore 1 as core 1 on socket 0 EAL: Detected lcore 2 as core 2 on socket 0 EAL: Detected lcore 3 as core 3 on socket 0 EAL: Detected lcore 4 as core 0 on socket 0 EAL: Detected lcore 5 as core 1 on socket 0 EAL: Detected lcore 6 as core 2 on socket 0 EAL: Detected lcore 7 as core 3 on socket 0 EAL: Support maximum 64 logical core(s) by configuration. EAL: Detected 8 lcore(s) EAL: cannot open VFIO container, error 2 (No such file or directory) EAL: VFIO support could not be initialized EAL: Searching for IVSHMEM devices... EAL: No IVSHMEM configuration found! EAL: Setting up memory... EAL: Ask a virtual area of 0x200000 bytes EAL: Virtual area found at 0x7fcb5b400000 (size =3D 0x200000) EAL: Ask a virtual area of 0x3000000 bytes EAL: Virtual area found at 0x7fcb58200000 (size =3D 0x3000000) EAL: Ask a virtual area of 0x3800000 bytes EAL: Virtual area found at 0x7fcb54800000 (size =3D 0x3800000) EAL: Ask a virtual area of 0x1000000 bytes EAL: Virtual area found at 0x7fcb53600000 (size =3D 0x1000000) EAL: Ask a virtual area of 0x400000 bytes EAL: Virtual area found at 0x7fcb53000000 (size =3D 0x400000) EAL: Ask a virtual area of 0x200000 bytes EAL: Virtual area found at 0x7fcb52c00000 (size =3D 0x200000) EAL: Requesting 64 pages of size 2MB from socket 0 EAL: TSC frequency is ~3691107 KHz EAL: Master core 1 is ready (tid=3D5b701940) EAL: Core 4 is ready (tid=3D513fc700) EAL: Core 3 is ready (tid=3D51bfd700) EAL: Core 2 is ready (tid=3D523fe700) EAL: PCI device 0000:03:00.0 on NUMA socket -1 EAL: probe driver: 8086:150e rte_igb_pmd EAL: PCI memory mapped at 0x7fcb5b645000 EAL: PCI memory mapped at 0x7fcb5b70a000 EAL: PCI device 0000:03:00.1 on NUMA socket -1 EAL: probe driver: 8086:150e rte_igb_pmd EAL: PCI memory mapped at 0x7fcb5b380000 EAL: PCI memory mapped at 0x7fcb5b706000 EAL: PCI device 0000:03:00.2 on NUMA socket -1 EAL: probe driver: 8086:150e rte_igb_pmd EAL: PCI memory mapped at 0x7fcb5b300000 EAL: PCI memory mapped at 0x7fcb5b641000 EAL: PCI device 0000:03:00.3 on NUMA socket -1 EAL: probe driver: 8086:150e rte_igb_pmd EAL: PCI memory mapped at 0x7fcb5b280000 EAL: PCI memory mapped at 0x7fcb5b63d000 EAL: PCI device 0000:06:00.0 on NUMA socket -1 EAL: probe driver: 8086:154d rte_ixgbe_pmd EAL: 0000:06:00.0 not managed by UIO driver, skipping EAL: PCI device 0000:06:00.1 on NUMA socket -1 EAL: probe driver: 8086:154d rte_ixgbe_pmd EAL: 0000:06:00.1 not managed by UIO driver, skipping PANIC in ovdk_mempools_init(): Cannot create ctrlmbuf mempool 'OVDK_Ctrlmbuf_Mempool' (Cannot allocate mem= ory) 1: [/home/cubiq/sothy/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_d= pdk.s o(rte_dump_stack+0x18) [0x7fcb5b7922d8]] =C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3= =C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2= =A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3= =C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2= =A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3=C2=A3 > > I'm not sure the CONFIG_ will be taken in account when generating > rte_config.h (see rte.sdkconfig.mk and scripts/gen-config-h.sh). But > maybe it's not related to your issue. Yes, Atleast build and check :-) Thanks a lot > > Regards, > Olivier