* [dpdk-users] Questions about huge page memory mappings between primary and secondary process
@ 2020-07-01 10:01 Pavel Vajarov
0 siblings, 0 replies; only message in thread
From: Pavel Vajarov @ 2020-07-01 10:01 UTC (permalink / raw)
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?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, back to index
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-01 10:01 [dpdk-users] Questions about huge page memory mappings between primary and secondary process Pavel Vajarov
DPDK usage discussions
Archives are clonable:
git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
Newsgroup available over NNTP:
AGPL code for this site: git clone https://public-inbox.org/ public-inbox