* [dpdk-dev] Setup script for xen ? @ 2014-07-08 20:24 Gary M 2014-07-09 0:45 ` Liu, Jijiang 0 siblings, 1 reply; 4+ messages in thread From: Gary M @ 2014-07-08 20:24 UTC (permalink / raw) To: dev Hi, New to the dpdk and just downloaded 1.7. I attempting to execute the test application (17) in Dom0 through the setup script. It hangs during or just after setting up memory. I know I'm doing something wrong, I just can't quickly figure out it is.. need some help !! I have UIO and KNI modules loaded and 64 pages NUMA shared memory. (I also tried 64 pages non-numa with the same result.) See: Option: 17 Enter hex bitmask of cores to execute test app on Example: to execute app on cores 0 to 7, enter 0xff bitmask: 0x01 Launching app EAL: Detected lcore 0 as core 1 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 2 on socket 0 EAL: Detected lcore 4 as core 3 on socket 0 EAL: Detected lcore 5 as core 3 on socket 0 EAL: Detected lcore 6 as core 4 on socket 0 EAL: Detected lcore 7 as core 4 on socket 0 EAL: Support maximum 64 logical core(s) by configuration. EAL: Detected 8 lcore(s) EAL: unsupported IOMMU type! EAL: VFIO support could not be initialized EAL: Setting up memory... Using debian jessie 3.14-1-amd64 #1 SMP Debian 3.14.4-1 (2014-05-13) x86_64 GNU/Linux with XEN 4.3.0 Any suggestions ? -gary ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] Setup script for xen ? 2014-07-08 20:24 [dpdk-dev] Setup script for xen ? Gary M @ 2014-07-09 0:45 ` Liu, Jijiang 2014-07-17 18:39 ` Gary M 0 siblings, 1 reply; 4+ messages in thread From: Liu, Jijiang @ 2014-07-09 0:45 UTC (permalink / raw) To: Gary M; +Cc: dev The setup script in Dom0 probably can't work. Could you execute DPDK application on Dom0 as follows: 1. insmod igb_uio.ko 2. insmod rte_dom0_mm.ko Before compiling DPDK, you should set CONFIG_RTE_LIBRTE_XEN_DOM0=y (# #Compile Xen domain0 support # CONFIG_RTE_LIBRTE_XEN_DOM0=y ) 3. echo 2048 > /sys/kernel/mm/dom0-mm/memsize-mB/mem_size 4. start DPDK application with --xen-dom0 option. ./testpmd -c f -n 3 --xen-dom0 -- -i --portmask=0x3 For more details how use DPDK application on Dom0, please look at DPDK Getting Start Guide document . -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Gary M Sent: Wednesday, July 09, 2014 4:25 AM To: dev@dpdk.org Subject: [dpdk-dev] Setup script for xen ? Hi, New to the dpdk and just downloaded 1.7. I attempting to execute the test application (17) in Dom0 through the setup script. It hangs during or just after setting up memory. I know I'm doing something wrong, I just can't quickly figure out it is.. need some help !! I have UIO and KNI modules loaded and 64 pages NUMA shared memory. (I also tried 64 pages non-numa with the same result.) See: Option: 17 Enter hex bitmask of cores to execute test app on Example: to execute app on cores 0 to 7, enter 0xff bitmask: 0x01 Launching app EAL: Detected lcore 0 as core 1 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 2 on socket 0 EAL: Detected lcore 4 as core 3 on socket 0 EAL: Detected lcore 5 as core 3 on socket 0 EAL: Detected lcore 6 as core 4 on socket 0 EAL: Detected lcore 7 as core 4 on socket 0 EAL: Support maximum 64 logical core(s) by configuration. EAL: Detected 8 lcore(s) EAL: unsupported IOMMU type! EAL: VFIO support could not be initialized EAL: Setting up memory... Using debian jessie 3.14-1-amd64 #1 SMP Debian 3.14.4-1 (2014-05-13) x86_64 GNU/Linux with XEN 4.3.0 Any suggestions ? -gary ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] Setup script for xen ? 2014-07-09 0:45 ` Liu, Jijiang @ 2014-07-17 18:39 ` Gary M 2014-07-30 2:11 ` Liu, Jijiang 0 siblings, 1 reply; 4+ messages in thread From: Gary M @ 2014-07-17 18:39 UTC (permalink / raw) To: Liu, Jijiang; +Cc: dev I'm back on it.. Thanks for the help.. testpmd works as it should, it reports packets sent and received on two ports. I'm still having issues with the other examples. testpmd works cmdline works helloworld works All other programs in the examples directory hang in a similar way setting up memory. eg. root@port22:~/dpdk-1.7.0/examples/exception_path/exception_path/x86_64-native-linuxapp-gcc# ./exception_path -c f -n 4 -- -p 3 -i 3 -o c --xen-dom0 EAL: Detected lcore 0 as core 1 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 2 on socket 0 EAL: Detected lcore 4 as core 3 on socket 0 EAL: Detected lcore 5 as core 3 on socket 0 EAL: Detected lcore 6 as core 4 on socket 0 EAL: Detected lcore 7 as core 4 on socket 0 EAL: Support maximum 64 logical core(s) by configuration. EAL: Detected 8 lcore(s) EAL: unsupported IOMMU type! EAL: VFIO support could not be initialized EAL: Setting up memory... The second time executed, they have a segmentation fault/ invalid op code at __delete_from_page_cache+0x122/0x130 any suggestions getting these other examples running ? I'm suspect its another config issue.. I'm including the stack trace: Jul 17 12:36:17 port22 kernel: [173619.514868] ------------[ cut here ]------------ Jul 17 12:36:17 port22 kernel: [173619.515061] invalid opcode: 0000 [#11] SMP Jul 17 12:36:17 port22 kernel: [173619.515265] Modules linked in: rte_dom0_mm(O) igb_uio(O) uio vfio loop xt_physdev iptable_filter ip_tables x_tables xen_netback xen_blkback xen_gntdev xen_evtchn xenfs xen_privcmd binfmt_misc nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc bridge stp llc sr_mod cdrom x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul sb_edac glue_helper ipmi_si edac_core dcdbas ablk_helper iTCO_wdt iTCO_vendor_support cryptd tpm_tis wmi pcspkr acpi_power_meter ipmi_msghandler tpm button joydev evdev lpc_ich mfd_core mei_me processor thermal_sys shpchp usb_storage mei ext4 crc16 mbcache jbd2 hid_generic usbhid hid sg sd_mod crc_t10dif crct10dif_common ahci libahci libata ehci_pci ehci_hcd scsi_mod usbcore usb_common ixgbe dca mdio tg3 ptp pps_core libphy [last unloaded: rte_dom0_mm] Jul 17 12:36:17 port22 kernel: [173619.521166] CPU: 7 PID: 12885 Comm: ip_fragmentatio Tainted: G D O 3.14-1-amd64 #1 Debian 3.14.4-1 Jul 17 12:36:17 port22 kernel: [173619.521290] Hardware name: Dell Inc. PowerEdge R620/01W23F, BIOS 2.2.2 01/16/2014 Jul 17 12:36:17 port22 kernel: [173619.521409] task: ffff8803fdc6f330 ti: ffff8800c83cc000 task.ti: ffff8800c83cc000 Jul 17 12:36:17 port22 kernel: [173619.521528] RIP: e030:[<ffffffff81120622>] [<ffffffff81120622>] __delete_from_page_cache+0x122/0x130 Jul 17 12:36:17 port22 kernel: [173619.521711] RSP: e02b:ffff8800c83cdd60 EFLAGS: 00010002 Jul 17 12:36:17 port22 kernel: [173619.521803] RAX: 0000000000f8a51f RBX: ffffea00011b1000 RCX: 00000000ffffffd0 Jul 17 12:36:17 port22 kernel: [173619.532999] RDX: 0000000000017302 RSI: 000000000000000a RDI: ffff88041a56f6c0 Jul 17 12:36:17 port22 kernel: [173619.533117] RBP: ffffea00011b1000 R08: 8038000000000030 R09: 0000000000000001 Jul 17 12:36:17 port22 kernel: [173619.533235] R10: 0000000000000000 R11: 0000000000000246 R12: ffff88007f8a65f0 Jul 17 12:36:17 port22 kernel: [173619.533353] R13: 0000000000000001 R14: 0000000000000000 R15: ffff88007f8a65f0 Jul 17 12:36:17 port22 kernel: [173619.533474] FS: 00007fc4b9c04840(0000) GS:ffff880415ee0000(0000) knlGS:0000000000000000 Jul 17 12:36:17 port22 kernel: [173619.533594] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 17 12:36:17 port22 kernel: [173619.533687] CR2: 00007fc4b8df9cd0 CR3: 000000038c42b000 CR4: 0000000000042660 Jul 17 12:36:17 port22 kernel: [173619.533806] Stack: Jul 17 12:36:17 port22 kernel: [173619.533890] ffffea00011b1000 ffff88007f8a65f0 0000000000000000 ffffffff8112065b Jul 17 12:36:17 port22 kernel: [173619.534237] 0000000000000000 0000000000000001 ffffea00011b1000 ffffffff811f82ab Jul 17 12:36:17 port22 kernel: [173619.534584] ffff88007f8a64a0 0000000000000000 0000000000000001 0000000000000000 Jul 17 12:36:17 port22 kernel: [173619.534932] Call Trace: Jul 17 12:36:17 port22 kernel: [173619.535019] [<ffffffff8112065b>] ? delete_from_page_cache+0x2b/0x60 Jul 17 12:36:17 port22 kernel: [173619.535115] [<ffffffff811f82ab>] ? truncate_hugepages+0xcb/0x180 Jul 17 12:36:17 port22 kernel: [173619.535210] [<ffffffff8114912d>] ? handle_mm_fault+0x48d/0xf10 Jul 17 12:36:17 port22 kernel: [173619.535305] [<ffffffff8119cef2>] ? __d_lookup+0x72/0x140 Jul 17 12:36:17 port22 kernel: [173619.535399] [<ffffffff811aa7dd>] ? __inode_wait_for_writeback+0x6d/0xc0 Jul 17 12:36:17 port22 kernel: [173619.535496] [<ffffffff8109e430>] ? autoremove_wake_function+0x30/0x30 Jul 17 12:36:17 port22 kernel: [173619.535592] [<ffffffff811f84bb>] ? hugetlbfs_evict_inode+0xb/0x20 Jul 17 12:36:17 port22 kernel: [173619.535686] [<ffffffff8119ec03>] ? evict+0xa3/0x190 Jul 17 12:36:17 port22 kernel: [173619.535778] [<ffffffff8119af58>] ? dentry_kill+0x1e8/0x230 Jul 17 12:36:17 port22 kernel: [173619.535870] [<ffffffff8119aff4>] ? dput+0x54/0xf0 Jul 17 12:36:17 port22 kernel: [173619.535962] [<ffffffff8118747b>] ? __fput+0x14b/0x210 Jul 17 12:36:17 port22 kernel: [173619.536055] [<ffffffff8107cda7>] ? task_work_run+0x97/0xd0 Jul 17 12:36:17 port22 kernel: [173619.536149] [<ffffffff81013979>] ? do_notify_resume+0x59/0x90 Jul 17 12:36:17 port22 kernel: [173619.536244] [<ffffffff814c7732>] ? int_signal+0x12/0x17 Jul 17 12:36:17 port22 kernel: [173619.536336] Code: 17 00 48 89 df ff 14 25 c8 48 82 81 5b 5d 41 5c c3 0f 1f 84 00 00 00 00 00 be 18 00 00 00 48 89 ef e8 63 c3 01 00 e9 32 ff ff ff <0f> 0b 66 66 66 2e 0f 1f 84 00 00 00 00 00 41 54 55 53 48 8b 07 Jul 17 12:36:17 port22 kernel: [173619.540475] RSP <ffff8800c83cdd60> Jul 17 12:36:17 port22 kernel: [173619.540563] ---[ end trace bb58961eb65f86ed ]--- cheers, On Tue, Jul 8, 2014 at 6:45 PM, Liu, Jijiang <jijiang.liu@intel.com> wrote: > The setup script in Dom0 probably can't work. > > Could you execute DPDK application on Dom0 as follows: > > 1. insmod igb_uio.ko > 2. insmod rte_dom0_mm.ko > Before compiling DPDK, you should set CONFIG_RTE_LIBRTE_XEN_DOM0=y > (# > #Compile Xen domain0 support > # > CONFIG_RTE_LIBRTE_XEN_DOM0=y > ) > > 3. echo 2048 > /sys/kernel/mm/dom0-mm/memsize-mB/mem_size > 4. start DPDK application with --xen-dom0 option. > ./testpmd -c f -n 3 --xen-dom0 -- -i --portmask=0x3 > > For more details how use DPDK application on Dom0, please look at DPDK > Getting Start Guide document . > > > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Gary M > Sent: Wednesday, July 09, 2014 4:25 AM > To: dev@dpdk.org > Subject: [dpdk-dev] Setup script for xen ? > > Hi, > > New to the dpdk and just downloaded 1.7. I attempting to execute the test > application (17) in Dom0 through the setup script. > > It hangs during or just after setting up memory. I know I'm doing > something wrong, I just can't quickly figure out it is.. need some help !! > > I have UIO and KNI modules loaded and 64 pages NUMA shared memory. (I also > tried 64 pages non-numa with the same result.) > > See: > Option: 17 > > > Enter hex bitmask of cores to execute test app on > Example: to execute app on cores 0 to 7, enter 0xff > bitmask: 0x01 > Launching app > EAL: Detected lcore 0 as core 1 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 2 on socket 0 > EAL: Detected lcore 4 as core 3 on socket 0 > EAL: Detected lcore 5 as core 3 on socket 0 > EAL: Detected lcore 6 as core 4 on socket 0 > EAL: Detected lcore 7 as core 4 on socket 0 > EAL: Support maximum 64 logical core(s) by configuration. > EAL: Detected 8 lcore(s) > EAL: unsupported IOMMU type! > EAL: VFIO support could not be initialized > EAL: Setting up memory... > > > Using debian jessie 3.14-1-amd64 #1 SMP Debian 3.14.4-1 (2014-05-13) > x86_64 GNU/Linux with XEN 4.3.0 > > Any suggestions ? > > -gary > ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] Setup script for xen ? 2014-07-17 18:39 ` Gary M @ 2014-07-30 2:11 ` Liu, Jijiang 0 siblings, 0 replies; 4+ messages in thread From: Liu, Jijiang @ 2014-07-30 2:11 UTC (permalink / raw) To: Gary M; +Cc: dev Hi Gary, From the following logs, it seems that you still use hugepae on Xen Dom0, actually, it not needed, the hugepage mechanism is not supported in Xen dom0. Jul 17 12:36:17 port22 kernel: [173619.535115] [<ffffffff811f82ab>] ? truncate_hugepages+0xcb/0x180 Jul 17 12:36:17 port22 kernel: [173619.535592] [<ffffffff811f84bb>] ? hugetlbfs_evict_inode+0xb/0x20 Don’t execute following configuration in Xen Dom environment . echo XXXX > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages Thanks Jijiang Liu From: Gary M [mailto:garym@oedata.com] Sent: Friday, July 18, 2014 2:39 AM To: Liu, Jijiang Cc: dev@dpdk.org Subject: Re: [dpdk-dev] Setup script for xen ? I'm back on it.. Thanks for the help.. testpmd works as it should, it reports packets sent and received on two ports. I'm still having issues with the other examples. testpmd works cmdline works helloworld works All other programs in the examples directory hang in a similar way setting up memory. eg. root@port22:~/dpdk-1.7.0/examples/exception_path/exception_path/x86_64-native-linuxapp-gcc#<mailto:root@port22:~/dpdk-1.7.0/examples/exception_path/exception_path/x86_64-native-linuxapp-gcc#> ./exception_path -c f -n 4 -- -p 3 -i 3 -o c --xen-dom0 EAL: Detected lcore 0 as core 1 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 2 on socket 0 EAL: Detected lcore 4 as core 3 on socket 0 EAL: Detected lcore 5 as core 3 on socket 0 EAL: Detected lcore 6 as core 4 on socket 0 EAL: Detected lcore 7 as core 4 on socket 0 EAL: Support maximum 64 logical core(s) by configuration. EAL: Detected 8 lcore(s) EAL: unsupported IOMMU type! EAL: VFIO support could not be initialized EAL: Setting up memory... The second time executed, they have a segmentation fault/ invalid op code at __delete_from_page_cache+0x122/0x130 any suggestions getting these other examples running ? I'm suspect its another config issue.. I'm including the stack trace: Jul 17 12:36:17 port22 kernel: [173619.514868] ------------[ cut here ]------------ Jul 17 12:36:17 port22 kernel: [173619.515061] invalid opcode: 0000 [#11] SMP Jul 17 12:36:17 port22 kernel: [173619.515265] Modules linked in: rte_dom0_mm(O) igb_uio(O) uio vfio loop xt_physdev iptable_filter ip_tables x_tables xen_netback xen_blkback xen_gntdev xen_evtchn xenfs xen_privcmd binfmt_misc nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc bridge stp llc sr_mod cdrom x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul sb_edac glue_helper ipmi_si edac_core dcdbas ablk_helper iTCO_wdt iTCO_vendor_support cryptd tpm_tis wmi pcspkr acpi_power_meter ipmi_msghandler tpm button joydev evdev lpc_ich mfd_core mei_me processor thermal_sys shpchp usb_storage mei ext4 crc16 mbcache jbd2 hid_generic usbhid hid sg sd_mod crc_t10dif crct10dif_common ahci libahci libata ehci_pci ehci_hcd scsi_mod usbcore usb_common ixgbe dca mdio tg3 ptp pps_core libphy [last unloaded: rte_dom0_mm] Jul 17 12:36:17 port22 kernel: [173619.521166] CPU: 7 PID: 12885 Comm: ip_fragmentatio Tainted: G D O 3.14-1-amd64 #1 Debian 3.14.4-1 Jul 17 12:36:17 port22 kernel: [173619.521290] Hardware name: Dell Inc. PowerEdge R620/01W23F, BIOS 2.2.2 01/16/2014 Jul 17 12:36:17 port22 kernel: [173619.521409] task: ffff8803fdc6f330 ti: ffff8800c83cc000 task.ti: ffff8800c83cc000 Jul 17 12:36:17 port22 kernel: [173619.521528] RIP: e030:[<ffffffff81120622>] [<ffffffff81120622>] __delete_from_page_cache+0x122/0x130 Jul 17 12:36:17 port22 kernel: [173619.521711] RSP: e02b:ffff8800c83cdd60 EFLAGS: 00010002 Jul 17 12:36:17 port22 kernel: [173619.521803] RAX: 0000000000f8a51f RBX: ffffea00011b1000 RCX: 00000000ffffffd0 Jul 17 12:36:17 port22 kernel: [173619.532999] RDX: 0000000000017302 RSI: 000000000000000a RDI: ffff88041a56f6c0 Jul 17 12:36:17 port22 kernel: [173619.533117] RBP: ffffea00011b1000 R08: 8038000000000030 R09: 0000000000000001 Jul 17 12:36:17 port22 kernel: [173619.533235] R10: 0000000000000000 R11: 0000000000000246 R12: ffff88007f8a65f0 Jul 17 12:36:17 port22 kernel: [173619.533353] R13: 0000000000000001 R14: 0000000000000000 R15: ffff88007f8a65f0 Jul 17 12:36:17 port22 kernel: [173619.533474] FS: 00007fc4b9c04840(0000) GS:ffff880415ee0000(0000) knlGS:0000000000000000 Jul 17 12:36:17 port22 kernel: [173619.533594] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 17 12:36:17 port22 kernel: [173619.533687] CR2: 00007fc4b8df9cd0 CR3: 000000038c42b000 CR4: 0000000000042660 Jul 17 12:36:17 port22 kernel: [173619.533806] Stack: Jul 17 12:36:17 port22 kernel: [173619.533890] ffffea00011b1000 ffff88007f8a65f0 0000000000000000 ffffffff8112065b Jul 17 12:36:17 port22 kernel: [173619.534237] 0000000000000000 0000000000000001 ffffea00011b1000 ffffffff811f82ab Jul 17 12:36:17 port22 kernel: [173619.534584] ffff88007f8a64a0 0000000000000000 0000000000000001 0000000000000000 Jul 17 12:36:17 port22 kernel: [173619.534932] Call Trace: Jul 17 12:36:17 port22 kernel: [173619.535019] [<ffffffff8112065b>] ? delete_from_page_cache+0x2b/0x60 Jul 17 12:36:17 port22 kernel: [173619.535115] [<ffffffff811f82ab>] ? truncate_hugepages+0xcb/0x180 Jul 17 12:36:17 port22 kernel: [173619.535210] [<ffffffff8114912d>] ? handle_mm_fault+0x48d/0xf10 Jul 17 12:36:17 port22 kernel: [173619.535305] [<ffffffff8119cef2>] ? __d_lookup+0x72/0x140 Jul 17 12:36:17 port22 kernel: [173619.535399] [<ffffffff811aa7dd>] ? __inode_wait_for_writeback+0x6d/0xc0 Jul 17 12:36:17 port22 kernel: [173619.535496] [<ffffffff8109e430>] ? autoremove_wake_function+0x30/0x30 Jul 17 12:36:17 port22 kernel: [173619.535592] [<ffffffff811f84bb>] ? hugetlbfs_evict_inode+0xb/0x20 Jul 17 12:36:17 port22 kernel: [173619.535686] [<ffffffff8119ec03>] ? evict+0xa3/0x190 Jul 17 12:36:17 port22 kernel: [173619.535778] [<ffffffff8119af58>] ? dentry_kill+0x1e8/0x230 Jul 17 12:36:17 port22 kernel: [173619.535870] [<ffffffff8119aff4>] ? dput+0x54/0xf0 Jul 17 12:36:17 port22 kernel: [173619.535962] [<ffffffff8118747b>] ? __fput+0x14b/0x210 Jul 17 12:36:17 port22 kernel: [173619.536055] [<ffffffff8107cda7>] ? task_work_run+0x97/0xd0 Jul 17 12:36:17 port22 kernel: [173619.536149] [<ffffffff81013979>] ? do_notify_resume+0x59/0x90 Jul 17 12:36:17 port22 kernel: [173619.536244] [<ffffffff814c7732>] ? int_signal+0x12/0x17 Jul 17 12:36:17 port22 kernel: [173619.536336] Code: 17 00 48 89 df ff 14 25 c8 48 82 81 5b 5d 41 5c c3 0f 1f 84 00 00 00 00 00 be 18 00 00 00 48 89 ef e8 63 c3 01 00 e9 32 ff ff ff <0f> 0b 66 66 66 2e 0f 1f 84 00 00 00 00 00 41 54 55 53 48 8b 07 Jul 17 12:36:17 port22 kernel: [173619.540475] RSP <ffff8800c83cdd60> Jul 17 12:36:17 port22 kernel: [173619.540563] ---[ end trace bb58961eb65f86ed ]--- cheers, On Tue, Jul 8, 2014 at 6:45 PM, Liu, Jijiang <jijiang.liu@intel.com<mailto:jijiang.liu@intel.com>> wrote: The setup script in Dom0 probably can't work. Could you execute DPDK application on Dom0 as follows: 1. insmod igb_uio.ko 2. insmod rte_dom0_mm.ko Before compiling DPDK, you should set CONFIG_RTE_LIBRTE_XEN_DOM0=y (# #Compile Xen domain0 support # CONFIG_RTE_LIBRTE_XEN_DOM0=y ) 3. echo 2048 > /sys/kernel/mm/dom0-mm/memsize-mB/mem_size 4. start DPDK application with --xen-dom0 option. ./testpmd -c f -n 3 --xen-dom0 -- -i --portmask=0x3 For more details how use DPDK application on Dom0, please look at DPDK Getting Start Guide document . -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org<mailto:dev-bounces@dpdk.org>] On Behalf Of Gary M Sent: Wednesday, July 09, 2014 4:25 AM To: dev@dpdk.org<mailto:dev@dpdk.org> Subject: [dpdk-dev] Setup script for xen ? Hi, New to the dpdk and just downloaded 1.7. I attempting to execute the test application (17) in Dom0 through the setup script. It hangs during or just after setting up memory. I know I'm doing something wrong, I just can't quickly figure out it is.. need some help !! I have UIO and KNI modules loaded and 64 pages NUMA shared memory. (I also tried 64 pages non-numa with the same result.) See: Option: 17 Enter hex bitmask of cores to execute test app on Example: to execute app on cores 0 to 7, enter 0xff bitmask: 0x01 Launching app EAL: Detected lcore 0 as core 1 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 2 on socket 0 EAL: Detected lcore 4 as core 3 on socket 0 EAL: Detected lcore 5 as core 3 on socket 0 EAL: Detected lcore 6 as core 4 on socket 0 EAL: Detected lcore 7 as core 4 on socket 0 EAL: Support maximum 64 logical core(s) by configuration. EAL: Detected 8 lcore(s) EAL: unsupported IOMMU type! EAL: VFIO support could not be initialized EAL: Setting up memory... Using debian jessie 3.14-1-amd64 #1 SMP Debian 3.14.4-1 (2014-05-13) x86_64 GNU/Linux with XEN 4.3.0 Any suggestions ? -gary ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-07-30 2:09 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2014-07-08 20:24 [dpdk-dev] Setup script for xen ? Gary M 2014-07-09 0:45 ` Liu, Jijiang 2014-07-17 18:39 ` Gary M 2014-07-30 2:11 ` Liu, Jijiang
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).