[dpdk-dev] Question about problem when calling rte_eal_init()

Junguk Cho jmanbal at gmail.com
Tue Jun 13 19:34:50 CEST 2017


Hi,

I use ovs-dpdk with one application which talks to ovs by using ring device
and "--proc-type=secondary" (secondary processes).
It generally works well, but sometimes it shows this error.

It seems it could not find correct memory mapping in the application.

2017-06-13 11:21:40.988 STDERR Thread-2 [INFO] EAL: Probing VFIO support...
2017-06-13 11:21:40.988 STDERR Thread-2 [INFO] EAL: WARNING: Address Space
Layout Randomization (ASLR) is enabled in the kernel.
2017-06-13 11:21:40.988 STDERR Thread-2 [INFO] EAL:    This may cause
issues with mapping memory into secondary processes
2017-06-13 11:21:40.989 STDERR Thread-2 [INFO] EAL: Could not mmap
17146314752 bytes in /dev/zero at [0x7f662c800000], got [0x7f6506000000] -
please use '--base-virtaddr' option
2017-06-13 11:21:40.989 STDERR Thread-2 [INFO] EAL: It is recommended to
disable ASLR in the kernel and retry running both primary and secondary
processes
2017-06-13 11:21:40.990 STDERR Thread-2 [INFO] PANIC in rte_eal_init():
2017-06-13 11:21:40.990 STDERR Thread-2 [INFO] Cannot init memory

I tried to disable ASLR, but it did not work.

Does anyone have the similar situation?
If so, would you please explain why this happens and how to avoid it?


Thanks,
Junguk


More information about the dev mailing list