DPDK usage discussions
 help / color / mirror / Atom feed
From: Pavel Vajarov <freakpv@gmail.com>
To: users <users@dpdk.org>
Subject: [dpdk-users] Questions about huge page memory mappings between primary and secondary process
Date: Wed, 1 Jul 2020 13:01:59 +0300	[thread overview]
Message-ID: <CAK9EM190yUO28c0dMcFfzo-5HJ=REdJfXJds4POMn6vZA6mamA@mail.gmail.com> (raw)

Hi there,

I have few questions related to this paragraph from the DPDK documentation
about Multi-process Limitations
```
The multi-process feature requires that the exact same hugepage memory
mappings be present in all applications. This makes secondary process
startup process generally unreliable. Disabling Linux security feature -
Address-Space Layout Randomization (ASLR) may help getting more consistent
mappings, but not necessarily more reliable - if the mappings are wrong,
they will be consistently wrong!
```

I can't understand why the memory mappings are not reliable in case the
ASLR is disabled?
Can somebody point me to documentation which explains more about this?
Also, what is the manifestation when the mappings are wrong: random crashes
and corruptions runtime or something else?

Thanks,
Pavel.

                 reply	other threads:[~2020-07-01 10:02 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='CAK9EM190yUO28c0dMcFfzo-5HJ=REdJfXJds4POMn6vZA6mamA@mail.gmail.com' \
    --to=freakpv@gmail.com \
    --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).