[dpdk-dev] [ovs-discuss] OVS DPDK|DPDK|ERR|interface dpdk0 start error:operation not permitted.
On Thu, Jul 28, 2016 at 2:29 AM, Yong Wang wrote: > >> On Jul 27, 2016, at 12:25 AM, sothy shan wrote: >> >> On Tue, Jul 26, 2016 at 6:32 PM, Mauricio Vasquez >> wrote: >>> Hello Sothy, >>> >>> Sorry for the delay in answering, some busy days here. >>> >>> >>> On 07/25/2016 12:03 PM, sothy shan wrote: >>>> >>>> Hello Mauricio, >>>> >>>> On Sun, Jul 24, 2016 at 12:17 PM, Mauricio Vasquez >>>> wrote: >>>>> >>>>> Hi Sothy, >>>>> >>>>> >>>>> On 07/21/2016 11:55 AM, sothy shan wrote: >>>>>> >>>>>> On Thu, Jul 21, 2016 at 11:43 AM, Mauricio Vasquez >>>>>> wrote: >>>>>>> >>>>>>> >>>>>>> On 07/21/2016 10:51 AM, sothy shan wrote: >>>>>>>> >>>>>>>> On Thu, Jul 21, 2016 at 10:41 AM, sothy shan >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> On Wed, Jul 20, 2016 at 9:02 PM, Mauricio Vasquez >>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> Hi Sothy, >>>>>>>>>> >>>>>>>>>> On 07/20/2016 07:40 PM, Aaron Conole wrote: >>>>>>>>>>> >>>>>>>>>>> sothy shan writes: >>>>>>>>>>> >>>>>>>>>>>> Hello all, >>>>>>>>>>> >>>>>>>>>>> Hi Sothy, >>>>>>>>>>> >>>>>>>>>>>> I followed the installion guide provided in the web site >>>>>>>>>>>> >>>>>>>>>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openvswitch_ovs_blob_master_INSTALL.DPDK.md-23ovstc=CwIBaQ=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs=44mSO5N5yEs4CeCdtQE0xt0F7J0p67_mApYVAzyYms0=vpaHcL64W3vOTY9P8yRZOdCJzbL_oWzZH6J2u4iT614=ojiXK7Tj1ANsHE_AlchVROP4R7LrgLQqVqTx7BjJQas= >>>>>>>>>>>> to install dpdk OVS. >>>>>>>>>>>> >>>>>>>>>>>> I am rurnning Ubuntu 14.04 (kernel 3.13). It is a VM running >>>>>>>>>>>> VMware. >>>>>>>>>>>> One intereface is enabled by VMXNET3. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> It is not clear for me, are you trying to install OvS within the VM? >>>>>>>>>> >>>>>>>>>>>> I used dpdk 16.04 >>>>>>>>>>>> Today I made clone of OVS (committ >>>>>>>>>>>> :bf32e3e2c029da18b5d6fd9210cb0ea12a1d0383). >>>>>>>>>>>> >>>>>>>>>>>> The following are different configuration compared to above link. >>>>>>>>>>>> >>>>>>>>>>>> sysctl -w vm.nr_hugepages=2048 >>>>>>>>>>>> Binded interface via igb_uio. >>>>>>>>>>>> >>>>>>>>>>>> Then followed same configuration to start ovs-vsswitch with dpdk. >>>>>>>>>>> >>>>>>>>>>> Can you please post the steps exactly that you followed? Which >>>>>>>>>>> user >>>>>>>>>>> you >>>>>>>>>>> were running as, etc? Can you also post how you expect packets to >>>>>>>>>>> arrive into the vm? >>>>>>>>>>> >>>>>>>>>>>> I am able to creatre bridge. When I create a port. It gives error >>>>>>>>>>>> message. >>>>>>>>>>> >>>>>>>>>>> Please show the steps for this, too. The exact commands you used. >>>>>>>>>>> >>>>>>>>>>>> When I check ovs-vswitchd.log file, >>>>>>>>>>>> >>>>>>>>>>>> There is warning that dpif_netlink|WARN|genric netlink family, >>>>>>>>>>>> ovs_datapath does not exist. The openvswitch kernel module may be >>>>>>>
[dpdk-dev] [ovs-discuss] OVS DPDK|DPDK|ERR|interface dpdk0 start error:operation not permitted.
On Tue, Jul 26, 2016 at 6:32 PM, Mauricio Vasquez wrote: > Hello Sothy, > > Sorry for the delay in answering, some busy days here. > > > On 07/25/2016 12:03 PM, sothy shan wrote: >> >> Hello Mauricio, >> >> On Sun, Jul 24, 2016 at 12:17 PM, Mauricio Vasquez >> wrote: >>> >>> Hi Sothy, >>> >>> >>> On 07/21/2016 11:55 AM, sothy shan wrote: >>>> >>>> On Thu, Jul 21, 2016 at 11:43 AM, Mauricio Vasquez >>>> wrote: >>>>> >>>>> >>>>> On 07/21/2016 10:51 AM, sothy shan wrote: >>>>>> >>>>>> On Thu, Jul 21, 2016 at 10:41 AM, sothy shan >>>>>> wrote: >>>>>>> >>>>>>> On Wed, Jul 20, 2016 at 9:02 PM, Mauricio Vasquez >>>>>>> wrote: >>>>>>>> >>>>>>>> Hi Sothy, >>>>>>>> >>>>>>>> On 07/20/2016 07:40 PM, Aaron Conole wrote: >>>>>>>>> >>>>>>>>> sothy shan writes: >>>>>>>>> >>>>>>>>>> Hello all, >>>>>>>>> >>>>>>>>> Hi Sothy, >>>>>>>>> >>>>>>>>>> I followed the installion guide provided in the web site >>>>>>>>>> >>>>>>>>>> https://github.com/openvswitch/ovs/blob/master/INSTALL.DPDK.md#ovstc >>>>>>>>>> to install dpdk OVS. >>>>>>>>>> >>>>>>>>>> I am rurnning Ubuntu 14.04 (kernel 3.13). It is a VM running >>>>>>>>>> VMware. >>>>>>>>>> One intereface is enabled by VMXNET3. >>>>>>>> >>>>>>>> >>>>>>>> It is not clear for me, are you trying to install OvS within the VM? >>>>>>>> >>>>>>>>>> I used dpdk 16.04 >>>>>>>>>> Today I made clone of OVS (committ >>>>>>>>>> :bf32e3e2c029da18b5d6fd9210cb0ea12a1d0383). >>>>>>>>>> >>>>>>>>>> The following are different configuration compared to above link. >>>>>>>>>> >>>>>>>>>> sysctl -w vm.nr_hugepages=2048 >>>>>>>>>> Binded interface via igb_uio. >>>>>>>>>> >>>>>>>>>> Then followed same configuration to start ovs-vsswitch with dpdk. >>>>>>>>> >>>>>>>>> Can you please post the steps exactly that you followed? Which >>>>>>>>> user >>>>>>>>> you >>>>>>>>> were running as, etc? Can you also post how you expect packets to >>>>>>>>> arrive into the vm? >>>>>>>>> >>>>>>>>>> I am able to creatre bridge. When I create a port. It gives error >>>>>>>>>> message. >>>>>>>>> >>>>>>>>> Please show the steps for this, too. The exact commands you used. >>>>>>>>> >>>>>>>>>> When I check ovs-vswitchd.log file, >>>>>>>>>> >>>>>>>>>> There is warning that dpif_netlink|WARN|genric netlink family, >>>>>>>>>> ovs_datapath does not exist. The openvswitch kernel module may be >>>>>>>>>> not >>>>>>>>>> loaded. >>>>>>>>> >>>>>>>>> This is definitely a problem. How did you start the ovs-vswitchd >>>>>>>>> daemon? >>>>>>>> >>>>>>>> >>>>>>>> This is not a problem Aaron, the ovs kernel module is not needed >>>>>>>> when >>>>>>>> ovs is >>>>>>>> compiled with DPDK. >>>>>>>>>> >>>>>>>>>> Then ERR: ERR|interface dpdk0 start error:operation not permitted. >>>>>>>>>> >>>>>>>>>> The corresponding port is loaded by dpdk driver as shown in >>>>>>>>>> dpdk_nic_bind --status. >>>>>>>>>> >>>>>>>>>&
[dpdk-dev] XL710 what is correct SFP+ connector vendor?
Hi! we are using XL710 4 portx10G. For the connetion can we use SFP+ connector from any vendor? Any specific SFP+ connector to test DPDK? We have some SFP+ connectoors. when connected, nothing is working. Thanks for your reponse. Best regards Sothy
[dpdk-dev] DPDK 1.7.1 error (PANIC in ovdk_vport_phy_port_init(): Cannot init NIC port '0' (Success))
Hi! I have one question to inii NIC port in DPDK 1.7.1. I got the following error/ EAL: PCI device :03:00.0 on NUMA socket -1 EAL: probe driver: 8086:150e rte_igb_pmd EAL: PCI memory mapped at 0x7fa5a5261000 EAL: PCI memory mapped at 0x7fa5a7538000 EAL: PCI device :03:00.1 on NUMA socket -1 EAL: probe driver: 8086:150e rte_igb_pmd EAL: PCI memory mapped at 0x7fa5a51e1000 EAL: PCI memory mapped at 0x7fa5a7534000 EAL: PCI device :03:00.2 on NUMA socket -1 EAL: probe driver: 8086:150e rte_igb_pmd EAL: PCI memory mapped at 0x7fa5a5161000 EAL: PCI memory mapped at 0x7fa5a753 EAL: PCI device :03:00.3 on NUMA socket -1 EAL: probe driver: 8086:150e rte_igb_pmd EAL: PCI memory mapped at 0x7fa5a50e1000 EAL: PCI memory mapped at 0x7fa5a50dd000 EAL: PCI device :06:00.0 on NUMA socket -1 EAL: probe driver: 8086:154d rte_ixgbe_pmd EAL: :06:00.0 not managed by UIO driver, skipping EAL: PCI device :06:00.1 on NUMA socket -1 EAL: probe driver: 8086:154d rte_ixgbe_pmd EAL: :06:00.1 not managed by UIO driver, skipping EAL: :06:00.0 not managed by UIO driver, skipping EAL: :06:00.1 not managed by UIO driver, skipping PANIC in ovdk_vport_phy_port_init(): Cannot init NIC port '0' (Success) 1: [/home/cubiq/sothy/dpdkovs/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so(rte_dump_stack+0x18) [0x7fa5a75bb768]] Abandon (core dumped) +++ THe above error I got when I run $./datapath/dpdk/ovs-dpdk -c 0x0F -n 4 --proc-type primary --huge-dir /dev/hugepages -- --stats_core=0 --stats_int=5 -p 0x03 I guess it is problem of DPDK to init PCI probe. Any guess or suggestion from error log. I am running Fedora 20, DPDK 1.7.1 and OVS DPDK 1.2./ Best regards Sothy
[dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
On Fri, Jan 16, 2015 at 5:35 PM, Olivier MATZ wrote: > Hi Sothy, > > On 01/16/2015 05:07 PM, sothy shan wrote: >> On Fri, Jan 16, 2015 at 3:27 PM, Olivier MATZ >> wrote: >>>> When I do with >>>> >>>> export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc" >>>> make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y >>>> install T="$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. sudo ./datapath/dpdk/ovs-dpdk -c 0x1E -n 4 --proc -type primary --huge-dir=/mnt/huge -- --stats_core=4 --stats=5 -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 0x20 bytes EAL: Virtual area found at 0x7fcb5b40 (size = 0x20) EAL: Ask a virtual area of 0x300 bytes EAL: Virtual area found at 0x7fcb5820 (size = 0x300) EAL: Ask a virtual area of 0x380 bytes EAL: Virtual area found at 0x7fcb5480 (size = 0x380) EAL: Ask a virtual area of 0x100 bytes EAL: Virtual area found at 0x7fcb5360 (size = 0x100) EAL: Ask a virtual area of 0x40 bytes EAL: Virtual area found at 0x7fcb5300 (size = 0x40) EAL: Ask a virtual area of 0x20 bytes EAL: Virtual area found at 0x7fcb52c0 (size = 0x20) EAL: Requesting 64 pages of size 2MB from socket 0 EAL: TSC frequency is ~3691107 KHz EAL: Master core 1 is ready (tid=5b701940) EAL: Core 4 is ready (tid=513fc700) EAL: Core 3 is ready (tid=51bfd700) EAL: Core 2 is ready (tid=523fe700) EAL: PCI device :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 :03:00.1 on NUMA socket -1 EAL: probe driver: 8086:150e rte_igb_pmd EAL: PCI memory mapped at 0x7fcb5b38 EAL: PCI memory mapped at 0x7fcb5b706000 EAL: PCI device :03:00.2 on NUMA socket -1 EAL: probe driver: 8086:150e rte_igb_pmd EAL: PCI memory mapped at 0x7fcb5b30 EAL: PCI memory mapped at 0x7fcb5b641000 EAL: PCI device :03:00.3 on NUMA socket -1 EAL: probe driver: 8086:150e rte_igb_pmd EAL: PCI memory mapped at 0x7fcb5b28 EAL: PCI memory mapped at 0x7fcb5b63d000 EAL: PCI device :06:00.0 on NUMA socket -1 EAL: probe driver: 8086:154d rte_ixgbe_pmd EAL: :06:00.0 not managed by UIO driver, skipping EAL: PCI device :06:00.1 on NUMA socket -1 EAL: probe driver: 8086:154d rte_ixgbe_pmd EAL: :06:00.1 not managed by UIO driver, skipping PANIC in ovdk_mempools_init(): Cannot create ctrlmbuf mempool 'OVDK_Ctrlmbuf_Mempool' (Cannot allocate memory) 1: [/home/cubiq/sothy/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.s o(rte_dump_stack+0x18) [0x7fcb5b7922d8]] ? > > 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
[dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
On Fri, Jan 16, 2015 at 3:27 PM, Olivier MATZ wrote:
> Hi Sothy,
>
> On 01/16/2015 03:10 PM, sothy shan wrote:
>> I guess you are completely wrong.
>>
>> Becasue when I do
>>
>> make config T=x86_64-ivshmem-linuxapp-gcc
>> make
>>
>> Testpmd works.
>>
>> When I do with
>>
>> export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
>> make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y
>> install T="$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
>
> As far as I know, RTE_SDK and RTE_TARGET must be defined when building
> an external application (like in examples), not when building test-pmd
> app which is a sdk built-in.
If I understand the your idea, I should compile and run DPDK OVS
directly rather than DPDK testpmd. Isnt it? I will try now this.
Before, I tries testpmd and then go for DPDK OVS.
>
> Also, I'm not sure passing a CONFIG_XYZ=y variable will be properly
> taken in account by the build system. Where did you found this syntax?
https://github.com/01org/dpdk-ovs/blob/development/docs/01_Installation.md
> The proper way is:
>
> make config T=x86_64-ivshmem-linuxapp-gcc O=my_dir
> ${EDITOR} my_dir/.config
> make O=my_dir
>
> One last comment, please be careful when copy/pasting commands in
> mails as there are typos in some of your commands. A reader could
> expect that your problem comes from this:
>
> $ export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
> $ echo $RTE_SDK
> /home/userexport
>
Sorry for mistake and I will do with care nw.
> Regards,
> Olivier
[dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
According to your argument, I compiled qemu in DPDK OVS as provided with command. After that, I compiled as stated here. cd DPDK # DPDK sub-directoryexport RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc" make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y install T="$RTE_TARGET" Then I try to run the command for testpmd. I got same error. Any idea where is the mistake? Thanks DPDK 1.7.1 in Fedora 21. PLease see the error here [cubiq at localhost dpdk-1.7.1]$ sudo ./x86_64-ivshmem-linuxapp-gcc/app/testpmd -c7 -n3 -- -i --nb-cores=2 --nb-ports=2 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: Searching for IVSHMEM devices... EAL: No IVSHMEM configuration found! EAL: Setting up memory... EAL: Ask a virtual area of 0x180 bytes EAL: Virtual area found at 0x7fbe5100 (size = 0x180) EAL: Ask a virtual area of 0x140 bytes EAL: Virtual area found at 0x7fbe4fa0 (size = 0x140) EAL: Ask a virtual area of 0x80 bytes EAL: Virtual area found at 0x7fbe52a0 (size = 0x80) EAL: Ask a virtual area of 0x200 bytes EAL: Virtual area found at 0x7fbe4d80 (size = 0x200) EAL: Ask a virtual area of 0x40 bytes EAL: Virtual area found at 0x7fbe4d20 (size = 0x40) EAL: Ask a virtual area of 0x40 bytes EAL: Virtual area found at 0x7fbe4cc0 (size = 0x40) EAL: Ask a virtual area of 0x40 bytes EAL: Virtual area found at 0x7fbe4c60 (size = 0x40) EAL: Ask a virtual area of 0x1c0 bytes EAL: Virtual area found at 0x7fbe4a80 (size = 0x1c0) EAL: Ask a virtual area of 0x40 bytes EAL: Virtual area found at 0x7fbe4a20 (size = 0x40) EAL: Requesting 64 pages of size 2MB from socket 0 EAL: TSC frequency is ~3691108 KHz EAL: Master core 0 is ready (tid=98377940) EAL: Core 2 is ready (tid=491fd700) EAL: Core 1 is ready (tid=499fe700) EAL: PCI device :06:00.0 on NUMA socket 0 EAL: probe driver: 8086:154d rte_ixgbe_pmd EAL: :06:00.0 not managed by VFIO driver, skipping EAL: :06:00.0 not managed by UIO driver, skipping EAL: PCI device :06:00.1 on NUMA socket 0 EAL: probe driver: 8086:154d rte_ixgbe_pmd EAL: :06:00.1 not managed by VFIO driver, skipping EAL: :06:00.1 not managed by UIO driver, skipping EAL: Error - exiting with code: 1 Cause: No probed ethernet devices - check that CONFIG_RTE_LIBRTE_IGB_PMD=y and that CONFIG_RTE_LIBRTE_EM_PMD=y and that CONFIG_RTE_LIBRTE_IXGBE_PMD=y in your configuration file On Fri, Dec 26, 2014 at 3:37 PM, Neil Horman wrote: > On Fri, Dec 26, 2014 at 09:01:13AM +0100, sothy shan wrote: > > On Thu, Dec 25, 2014 at 6:08 PM, Neil Horman > wrote: > > > > > On Thu, Dec 25, 2014 at 10:11:51AM +0100, sothy shan wrote: > > > > On Wed, Dec 24, 2014 at 4:04 PM, Neil Horman > > > wrote: > > > > > > > > > On Wed, Dec 24, 2014 at 02:26:21PM +0100, sothy shan wrote: > > > > > > Hello! > > > > > > > > > > > > I am playing with DPDK 1.7.1 in Fedora. > > > > > > > > > > > > When I do like this: > > > > > > > > > > > > export RTE_SDK=$(pwd)export > RTE_TARGET="x86_64-ivshmem-linuxapp-gcc" > > > > > > make install T="$RTE_TARGET" > > > > > > > > > > > > It worked. Means Testpmd is running. > > > > > > > > > > > > When I run as mentioned below: > > > > > > > > > > > > make CONFIG_RTE_BUILD_SHARED_LIB=y install T="$RTE_TARGET" > > > > > > > > > > > > Build is sucess. But Testpmd gives error. > > > > > > > > > > > > Error is : > > > > > > > > > > > The dpdk ivshmem build assumes the presence of ivshmem devices as > > > plumbed > > > > > by > > > > > qemu virtual guests. If you don't have a qemu guest running dpdk > won't > > > > > find any > > > > > shared memory devices, which is exactly what you are seeing. That > > > said, > > > > > even if > > > > > you are running qemu guests, IIRC Fedora doesn't enable ivshmem > because > > > > > the code > > > > > has some security and behavioral issues still I think. You'll > need t
[dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
On Thu, Dec 25, 2014 at 6:08 PM, Neil Horman wrote: > On Thu, Dec 25, 2014 at 10:11:51AM +0100, sothy shan wrote: > > On Wed, Dec 24, 2014 at 4:04 PM, Neil Horman > wrote: > > > > > On Wed, Dec 24, 2014 at 02:26:21PM +0100, sothy shan wrote: > > > > Hello! > > > > > > > > I am playing with DPDK 1.7.1 in Fedora. > > > > > > > > When I do like this: > > > > > > > > export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc" > > > > make install T="$RTE_TARGET" > > > > > > > > It worked. Means Testpmd is running. > > > > > > > > When I run as mentioned below: > > > > > > > > make CONFIG_RTE_BUILD_SHARED_LIB=y install T="$RTE_TARGET" > > > > > > > > Build is sucess. But Testpmd gives error. > > > > > > > > Error is : > > > > > > > The dpdk ivshmem build assumes the presence of ivshmem devices as > plumbed > > > by > > > qemu virtual guests. If you don't have a qemu guest running dpdk won't > > > find any > > > shared memory devices, which is exactly what you are seeing. That > said, > > > even if > > > you are running qemu guests, IIRC Fedora doesn't enable ivshmem because > > > the code > > > has some security and behavioral issues still I think. You'll need to > > > rebuild > > > qemu to add support for it. > > > > > > > My understanding is that It is problem of enabling > > CONFIG_RTE_BUILD_SHARED_LIB=y in make command, I am able to build target > of > > x86_64-ivshmem-linuxapp-gcc alone without shared_lib flag. I suspect an > > error because of shared lib flag. > > > What exactly do you think that problem is? You just said in your > origional note that you are able to build the sdk and test apps without > issue > (with or without building them as DSO's). The problem comes in when you > run > the app, and I expect you get the same error with both static and dynamic > builds. > > The problem seems obvious to me. DPDK cannot find any ivshmem devices on > your > system when it loads (look at the code in rte_eal_ivshmem_init). The error > message you see gets output if you don't generate an ivshmem_config, which > happens (among a few other reasons), if you don't have any ivshmem devices > created on your system > > Neil > Do you have any hints for these messsages? EAL: Error - exiting with code: 1 Cause: No probed ethernet devices - check that CONFIG_RTE_LIBRTE_IGB_PMD=y and that CONFIG_RTE_LIBRTE_EM_PMD=y and that CONFIG_RTE_LIBRTE_IXGBE_PMD=y in your configuration file Is that with IVSHMEM device or physical devices? I guess it is physical device problem? Thank you Sothy
[dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
On Wed, Dec 24, 2014 at 4:04 PM, Neil Horman wrote: > On Wed, Dec 24, 2014 at 02:26:21PM +0100, sothy shan wrote: > > Hello! > > > > I am playing with DPDK 1.7.1 in Fedora. > > > > When I do like this: > > > > export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc" > > make install T="$RTE_TARGET" > > > > It worked. Means Testpmd is running. > > > > When I run as mentioned below: > > > > make CONFIG_RTE_BUILD_SHARED_LIB=y install T="$RTE_TARGET" > > > > Build is sucess. But Testpmd gives error. > > > > Error is : > > > The dpdk ivshmem build assumes the presence of ivshmem devices as plumbed > by > qemu virtual guests. If you don't have a qemu guest running dpdk won't > find any > shared memory devices, which is exactly what you are seeing. That said, > even if > you are running qemu guests, IIRC Fedora doesn't enable ivshmem because > the code > has some security and behavioral issues still I think. You'll need to > rebuild > qemu to add support for it. > My understanding is that It is problem of enabling CONFIG_RTE_BUILD_SHARED_LIB=y in make command, I am able to build target of x86_64-ivshmem-linuxapp-gcc alone without shared_lib flag. I suspect an error because of shared lib flag. Sothy > > Neil > >
[dpdk-dev] librte_distributor.so: cannot open shared object file
Hi! I am in fedora 21. I build sucesfully. I set the LD_LIBRARY_PATH. When I run the testpmd file, I am getting above error. Thank for your help. [cubiq at localhost dpdk-1.7.1]$ echo $LD_LIBRARY_PATH /home/cubiq/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib [cubiq at localhost dpdk-1.7.1]$ sudo ./x86_64-ivshmem-linuxapp-gcc/app/testpmd [sudo] password for cubiq: ./x86_64-ivshmem-linuxapp-gcc/app/testpmd: error while loading shared libraries: librte_distributor.so: cannot open shared object file: No such file or directory [cubiq at localhost dpdk-1.7.1]$ Best regards Sothy
[dpdk-dev] Build sucess DPDK 1.7.1 in UBunutu, testpmd failed with librte_distributor.so
Hi! I am trying these commands. based on suggestion http://dpdk.org/ml/archives/dev/2014-October/006247.html $RTE_TARGET=/x86_64-ivshmem-linuxapp-gcc $make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y install T="$RTE_TARGET" EXTRA_LDFLAGS=--no-as-needed Build sucessfully. Before it is not build. Thanks. But when I try testpmd script, it gives error:: ./testpmd: error while loading shared libraries: librte_distributor.so: cannot open shared object file: No such file or directory So it means that there are some problem in build. If u know where is the problem, please let me know. Best regards Sothy
[dpdk-dev] rte_config.h missing in DPDK 1.7.1
Hi Marc! Thank for your response. But I tried double check.Propelly set those values. Actually I found the file inside x86_64-native-linuxapp-gcc/include/rte_config.h. But when I compile DPDK OVS, it does not find the file. I got same error/ lib/dpdk-link.c:25:24: fatal error: rte_config.h: No such file or directory #include Best regards Sothy On Thu, Dec 11, 2014 at 12:22 PM, Marc Sune wrote: > This usually shows up when you are attempting to compile your DPDK > application without properly defining RTE_SDK and RTE_TARGET (where DPDK > source resides). > > Just double check if they are properly defined and exported > > marc > > > On 11/12/14 12:17, sothy shan wrote: > >> Hi! >> I am seeking help on installing DPDK OVS with DPDK 1.7.1 on ubuntu 14.04. >> If any body knows solutin, please let me. >> >> I compile in a typical way for DPDK 1.7.1 with x86_64_native-linuxaap-gcc. >> command: >> >> make config T=x86_64-native-linuxapp-gcc >> make >> >> It compiled and worked. I am able to run testpmd appplication also. >> >> But I start to compile DPDK OVS, DPDK OVS gives error. The erros is : >> >> CC lib/dpdk-link.lo >> lib/dpdk-link.c:25:24: fatal error: rte_config.h: No such file or >> directory >> #include >> >> Please help where is wrong. WhenI search in DPDK 1.7.1 folder, I >> couldnt find rte_config.h file. >> >> Thank you very much for your help. >> >> Best regards >> Sothy >> > >
[dpdk-dev] rte_config.h missing in DPDK 1.7.1
Hi! I am seeking help on installing DPDK OVS with DPDK 1.7.1 on ubuntu 14.04. If any body knows solutin, please let me. I compile in a typical way for DPDK 1.7.1 with x86_64_native-linuxaap-gcc. command: make config T=x86_64-native-linuxapp-gcc make It compiled and worked. I am able to run testpmd appplication also. But I start to compile DPDK OVS, DPDK OVS gives error. The erros is : CC lib/dpdk-link.lo lib/dpdk-link.c:25:24: fatal error: rte_config.h: No such file or directory #include Please help where is wrong. WhenI search in DPDK 1.7.1 folder, I couldnt find rte_config.h file. Thank you very much for your help. Best regards Sothy
[dpdk-dev] librte_distributor.so: cannot open shared object file: No such file or directory
Hi! I compiled DPDK v1.7.1 on ubunutu 14.04. I used following commands to compille. cd DPDKexport RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc" make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y install T="$RTE_TARGET" I mounted hugepages and added ports into igb_uio drivers also. When I run test commands within dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/app$ ./testpmd, I am getting following error. /testpmd: error while loading shared libraries: librte_distributor.so: cannot open shared object file: No such file or directory Do you have idea? Best regards Sothy
[dpdk-dev] collect2: error: ld returned 1 exit status -->> DPDK 1.7.1
Hi! I run the command below and got an error with Collect2. May I know why? Best regards Sothy Command:>>> $export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc" $make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y install T="$RTE_TARGET" Error:>>> == Build app/test-acl CC main.o LD testacl /home/cubiq/sothy/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: r?f?rence ind?finie vers ? log2 ? /home/cubiq/sothy/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: r?f?rence ind?finie vers ? ceil ? /home/cubiq/sothy/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: r?f?rence ind?finie vers ? pow ? /home/cubiq/sothy/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: r?f?rence ind?finie vers ? round ? collect2: error: ld returned 1 exit status make[5]: *** [testacl] Erreur 1 make[4]: *** [test-acl] Erreur 2 make[3]: *** [app] Erreur 2 make[2]: *** [all] Erreur 2 make[1]: *** [x86_64-ivshmem-linuxapp-gcc_install] Erreur 2 make: *** [install] Erreur 2
[dpdk-dev] system level L3 performance
Hi! Do you know any definition of system level L3 performance? I was reading slides of IDF14. They are saying they achieved 320 Gbps of systel level L3 performance using DPDK 1.7.O in Intel Xeon E5_2699 V3 But they used two 10G ports. I wondering the relationship. Thank for your explanation. Best regards Sothy .
[dpdk-dev] rte_eth_dev_configure
Thanks and it is working and help me a lot. On Thu, Jul 24, 2014 at 3:05 PM, Thomas Monjalon wrote: > 2014-07-24 15:00, sothy shan: > > I have problem when I try dpdk ovs with DPDK 1.7. DPDK 1.7 alone working > > well. > [...] > > I am not sure when I using DPDK ovs, how to debug at DPDK 1.7.0 code. I > > guess I need to enable to print PMD_DEBUG_TRACE message. At this point, > > DPDK ovs message is only printed. > > You should enable CONFIG_RTE_LIBRTE_ETHDEV_DEBUG before compiling. > > > I too suspect it is problem with port_conf message. Not sure. First I > need > > to know how to use PMD_DEBUG_TRACE with DPDK_ovs. > > > > You understand my question? > > Yes I understand that you should enable debugging and ask for help on the > right mailling list. > If DPDK alone works well, we cannot do anything for you. > > -- > Thomas >
[dpdk-dev] rte_eth_dev_configure
Hello! I am trying to use DPDK ovs (development branch) with DPDK1.7. There is an error when running ovs_dpdk command. Error is PANIC in ovdk_vport_phy_port_init. Cannot initi NIC port 0 (-22). Based on my search within code, rte_eth_dev_configure gives an error with code -22. My question is that how to debug or print the PMD_DEBUG_TRACE into file or terminal when running ovs-dpdk? Second, any clue why rte_eth_dev_configure give an error with code -22? Thanks for your help. Best regards Sothy
[dpdk-dev] implicit declaration of function rte_igb_pmd_init()
Hi All! I have an error when I compile latest DPDK ovs code. DPDK version is 1.7. Error is: CC main.o CC init.o In file included from /home/cubiq/sothy/dpdk-ovs/openvswitch/datapath/dpdk/init.c:42:0: /home/cubiq/sothy/dpdk-ovs/openvswitch/datapath/dpdk/init_drivers.h: In function ?init_drivers?: /home/cubiq/sothy/dpdk-ovs/openvswitch/datapath/dpdk/init_drivers.h:49:4: error: implicit declaration of function ?rte_igb_pmd_init? [-Werror=implicit-function-declaration] (rte_igb_pmd_init() < 0) || ^ /home/cubiq/sothy/dpdk-ovs/openvswitch/datapath/dpdk/init_drivers.h:52:4: error: implicit declaration of function ?rte_ixgbe_pmd_init? [-Werror=implicit-function-declaration] (rte_ixgbe_pmd_init() < 0) || ^ cc1: all warnings being treated as errors make[4]: *** [init.o] Erreur 1 make[3]: *** [all] Erreur 2 make[3]: quittant le r?pertoire ? /home/cubiq/sothy/dpdk-ovs/openvswitch/datapath/dpdk ? make[2]: *** [app] Erreur 2 make[2]: quittant le r?pertoire ? /home/cubiq/sothy/dpdk-ovs/openvswitch/datapath/dpdk ? make[1]: *** [all-recursive] Erreur 1 make[1]: quittant le r?pertoire ? /home/cubiq/sothy/dpdk-ovs/openvswitch ? make: *** [all] Erreur === THanks for your help. Best regardss Sothy
[dpdk-dev] Intel DPDK: exception_path:RTE_ARCH
On Wed, Jul 2, 2014 at 12:04 PM, sothy shan wrote: > > > > On Wed, Jul 2, 2014 at 12:00 PM, Thomas Monjalon < > thomas.monjalon at 6wind.com> wrote: > >> 2014-07-02 12:56, Alex Markuze: >> > On Wed, Jul 2, 2014 at 12:48 PM, sothy shan >> wrote: >> > > I started playing Intel DPDK example. I used to compile exception_path >> > > code. >> > > When I do make command "make", I got an error, >> > > >> > > RTE_ARCH is not set. So I set the variable via terminal bash using >> > > >> > > export RTE_ARCH=x86_64 >> > > >> > > Stilll it is not working. Any wrong anywhere? >> > >> > You need, to define the following variables before compiling, please >> refer >> > to the DPDK documentation. >> > >> > export RTE_TARGET=x86_64-native-linuxapp-gcc >> > >> > export RTE_SDK=/home/user/dpdk >> >> You can also try to build all examples with these commands: >> RTE_TARGET=x86_64-native-linuxapp-gcc >> make T=$RTE_TARGET install >> make T=$RTE_TARGET examples O=$RTE_TARGET/examples >> >> (with DPDK >= 1.7) >> >> > > When using DPDK 1.7, example/exception_path works. now playing with it. thx
[dpdk-dev] Intel DPDK: exception_path:RTE_ARCH
I followed and error is there again.
See more description here: make didnot worked. I still use 1.6. :-)
cubiq at WKS-LNX-006:~$ ${RTE_SDK}
cubiq at WKS-LNX-006:~$ ${RTE_TARGET}
cubiq at WKS-LNX-006:~$ export RTE_SDK=/home/cubiq/sothy/dpdk-1.6.0r2
cubiq at WKS-LNX-006:~$ export RTE_TARGET=x86_64-native-linuxapp-gcc
cubiq at WKS-LNX-006:~$ cd ${RTE_SDK}
cubiq at WKS-LNX-006:~/sothy/dpdk-1.6.0r2$ cd examples/exception_path/
cubiq at WKS-LNX-006:~/sothy/dpdk-1.6.0r2/examples/exception_path$ make
/home/cubiq/sothy/dpdk-1.6.0r2/mk/rte.extvars.mk:71:
/home/cubiq/sothy/dpdk-1.6.0r2/x86_64-native-linuxapp-gcc/.config: Aucun
fichier ou dossier de ce type
/home/cubiq/sothy/dpdk-1.6.0r2/mk/rte.vars.mk:99: *** RTE_ARCH is not
defined. Arr?t.
cubiq at WKS-LNX-006:~/sothy/dpdk-1.6.0r2/examples/exception_path$
On Wed, Jul 2, 2014 at 11:56 AM, Alex Markuze wrote:
> You need, to define the following variables before compiling, please refer
> to the DPDK documentation.
>
>
> export RTE_TARGET=x86_64-native-linuxapp-gcc
>
> export RTE_SDK=/home/user/dpdk
>
>
> On Wed, Jul 2, 2014 at 12:48 PM, sothy shan wrote:
>
>> Hello!
>>
>> I started playing Intel DPDK example. I used to compile exception_path
>> code.
>> When I do make command "make", I got an error,
>>
>> RTE_ARCH is not set. So I set the variable via terminal bash using
>>
>> export RTE_ARCH=x86_64
>>
>> Stilll it is not working. Any wrong anywhere?
>>
>> Thanks for your reponse.
>>
>> Best regards
>> Sothy
>>
>
>
[dpdk-dev] Intel DPDK: exception_path:RTE_ARCH
On Wed, Jul 2, 2014 at 12:00 PM, Thomas Monjalon wrote: > 2014-07-02 12:56, Alex Markuze: > > On Wed, Jul 2, 2014 at 12:48 PM, sothy shan wrote: > > > I started playing Intel DPDK example. I used to compile exception_path > > > code. > > > When I do make command "make", I got an error, > > > > > > RTE_ARCH is not set. So I set the variable via terminal bash using > > > > > > export RTE_ARCH=x86_64 > > > > > > Stilll it is not working. Any wrong anywhere? > > > > You need, to define the following variables before compiling, please > refer > > to the DPDK documentation. > > > > export RTE_TARGET=x86_64-native-linuxapp-gcc > > > > export RTE_SDK=/home/user/dpdk > > You can also try to build all examples with these commands: > RTE_TARGET=x86_64-native-linuxapp-gcc > make T=$RTE_TARGET install > make T=$RTE_TARGET examples O=$RTE_TARGET/examples > > (with DPDK >= 1.7) > >
[dpdk-dev] Intel DPDK: exception_path:RTE_ARCH
Hello! I started playing Intel DPDK example. I used to compile exception_path code. When I do make command "make", I got an error, RTE_ARCH is not set. So I set the variable via terminal bash using export RTE_ARCH=x86_64 Stilll it is not working. Any wrong anywhere? Thanks for your reponse. Best regards Sothy
