DPDK patches and discussions
 help / color / mirror / Atom feed
From: Junguk Cho <jmanbal@gmail.com>
To: "users@dpdk.org" <users@dpdk.org>, dev@dpdk.org
Subject: [dpdk-dev] Question about problem when calling rte_eal_init()
Date: Tue, 13 Jun 2017 11:34:50 -0600	[thread overview]
Message-ID: <CAMNaBtORvu6-X7azK3aMQw+SuneEbgxQZAVUnx5zRmDmwytcbQ@mail.gmail.com> (raw)

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

                 reply	other threads:[~2017-06-13 17:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAMNaBtORvu6-X7azK3aMQw+SuneEbgxQZAVUnx5zRmDmwytcbQ@mail.gmail.com \
    --to=jmanbal@gmail.com \
    --cc=dev@dpdk.org \
    --cc=users@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).