From: Murillo <imurillo006@ehu.es>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK xen-dom0 not working at all
Date: Thu, 30 Oct 2014 16:10:54 +0100 [thread overview]
Message-ID: <545254FE.3080200@ehu.es> (raw)
In-Reply-To: <1ED644BD7E0A5F4091CF203DAFB8E4CC01D8438A@SHSMSX101.ccr.corp.intel.com>
I am sorry, I missed it during the redaction of the email. I executed it
correcly. When I do "cat /sys/kernel/mm/dom0-mm/memsize-mB/memsize" it
prints 2048.
Thank you for your answer and your time.
El 30/10/14 a las 13:59, Liu, Jijiang escribió:
> ">" was missed in the following command.
>
> echo 2048 > /sys/kernel/mm/dom0-mm/memsize-mB/memsize
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Murillo
>> Sent: Thursday, October 30, 2014 6:27 PM
>> To: dev@dpdk.org
>> Subject: [dpdk-dev] DPDK xen-dom0 not working at all
>>
>> English is not my native language; please excuse typing errors.
>>
>>
>> I am new to DPDK with Xen, but I am able to run DPDK applications without xen
>> using hugepages. But when I try to do it in xen-dom0 it does not work. Let me
>> explain:
>>
>>
>> I have followed the intructions on the Getting Started Guide, so I execute the next
>> steps:
>>
>>
>> Dpdk/config/common_linuxapp
>>
>> CONFIG_RTE_LIBRTE_XEN_DOM0=y
>>
>> make config T=x86_64-native-linuxapp-gcc
>>
>> make install T=x86_64-native-linuxapp-gcc
>>
>> sudo modprobe uio
>>
>> sudo insmod x86_64-native-linuxapp-gcc/kmod/igb_uio.ko
>>
>> sudo insmod x86_64-native-linuxapp-gcc/kmod/rte_dom0_mm.ko
>> rsv_memsize=2048
>>
>> echo 2048 /sys/kernel/mm/dom0-mm/memsize-mB/memsize
>>
>> tools/dpdk_nic_bind.py --bind=igb_uio $(tools/dpdk_nic_bind.py --status
>> | sed -rn 's,.* if=([^ ]*).*igb_uio *$,\1,p')
>>
>>
>>
>> The main problem appears when I try to execute helloworld for example.
>>
>> Sudo ./build/helloworld -c 0xf -n 2 –xen-dom0
>>
>> Output:
>>
>> EAL: Detected lcore 0 as core 0 on socket 0
>>
>> EAL: Detected lcore 1 as core 0 on socket 0
>>
>> EAL: Detected lcore 2 as core 1 on socket 0
>>
>> …
>>
>> EAL: Detected lcore 39 as core 12 on socket 0
>>
>> EAL: Support maximum 64 logical core(s) by configuration.
>>
>> EAL: Detected 40 lcore(s)
>>
>> And it stops.
>>
>>
>>
>> If I execute dmegs I get the following:
>>
>> [ 1098.120193] helloworld[20116] trap invalid opcode ip:45adb7
>> sp:7fff4cf7e150 error:0 in helloworld[400000+115000]
>>
>>
>>
>> Here are the characteristics of the server:
>>
>> DPDK 1.7.1
>>
>> xm info:
>>
>> host : vh05
>>
>> release : 3.5.0-47-generic
>>
>> version : #71~precise1-Ubuntu SMP Wed Feb 19 22:02:52 UTC 2014
>>
>> machine : x86_64
>>
>> nr_cpus : 40
>>
>> nr_nodes : 2
>>
>> cores_per_socket : 10
>>
>> threads_per_core : 2
>>
>> cpu_mhz : 3000
>>
>> hw_caps :
>> bfebfbff:2c100800:00000000:00007f40:73bee3ff:00000000:00000001:00000281
>>
>> virt_caps : hvm hvm_directio
>>
>> total_memory : 32722
>>
>> free_memory : 28196
>>
>> free_cpus : 0
>>
>> xen_major : 4
>>
>> xen_minor : 1
>>
>> xen_extra : .5
>>
>> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p
>> hvm-3.0-x86_64
>>
>> xen_scheduler : credit
>>
>> xen_pagesize : 4096
>>
>> platform_params : virt_start=0xffff800000000000
>>
>> xen_changeset : unavailable
>>
>> xen_commandline : placeholder dom0_mem=4096M max_loop=64
>>
>> cc_compiler : gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
>>
>> cc_compile_by : stefan.bader
>>
>> cc_compile_domain : canonical.com
>>
>> cc_compile_date : Wed Feb 19 15:32:59 UTC 2014
>>
>> xend_config_format : 4
>>
>>
>>
>> Thank you in anvanced.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
next prev parent reply other threads:[~2014-10-30 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 10:26 Murillo
2014-10-30 12:59 ` Liu, Jijiang
2014-10-30 15:10 ` Murillo [this message]
2014-11-03 2:47 ` Liu, Jijiang
2014-11-03 8:58 ` Murillo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=545254FE.3080200@ehu.es \
--to=imurillo006@ehu.es \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).