From: "David Coen" <d.coen@resi.it>
To: <users@dpdk.org>
Subject: [dpdk-users] R: Issue with more Cores assigned: Cannot mmap device resource file
Date: Wed, 15 Mar 2017 15:27:31 +0100 [thread overview]
Message-ID: <001601d29d98$4d92c5a0$e8b850e0$@resi.it> (raw)
Hi Kai, I agree with you.
Hi have quite the same issue, a primary application and a secondary one
running, sometimes, with more than 4 cores.
I'm using DPDK 16.11 on RedHat 6.7.
Till now I solved in this way:
- Disabling ASLR by adding those two lines to "/etc/sysctl.conf":
# Disable Address Space Layout Randomization (ASLR) (needed
by DPDK)
kernel.randomize_va_space = 0
- Getting virtual address of the first (the one with the minimum address
value) memory segment returned from the function "rte_eal_get_physmem_layout
()", called from a "dummy" primary application used only to get this
address.
- Passing the above virtual address as a parameter for the "real" primary
application using the " --base-virtaddr= " dpdk command line option. When
secondary app starts, it all goes well with the specified base address.
I've tested this solution on different servers and it's always ok.
I think that there is some kind of limitation on DPDK primary/secondary
initialization process that could be improved.
Regards,
David
reply other threads:[~2017-03-15 14:29 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='001601d29d98$4d92c5a0$e8b850e0$@resi.it' \
--to=d.coen@resi.it \
--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).