From: Venkat Thummala <venkat.thummala.1978@gmail.com>
To: Uri Sidler <uri.sidler@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] sharing rte_malloc() address between processes.
Date: Tue, 10 Jun 2014 17:59:32 +0530 [thread overview]
Message-ID: <CAF5bpL_sK5Hv26oJ-QKorBHR2Ty1YETKZS8kVB8Yhq=fsB8jRA@mail.gmail.com> (raw)
In-Reply-To: <CACxZdGooiEo8cf_acBa95PthTPbCmr2oG=JLFFg+sHy1wQT-ag@mail.gmail.com>
Hi,
Yo
• The multi-process feature requires that the exact same hugepage memory
mappings be present in all applications. The Linux security feature -
Address-Space
Layout Randomization (ASLR) can interfere with this mapping, so it may be
necessary to disable this feature in order to reliably run multi-process
applications.
On 10 June 2014 17:17, Uri Sidler <uri.sidler@gmail.com> wrote:
> How can I share the addresses between processes?
> Is there a simple way of doing so?
>
> thanks,
> Shirley.
>
next prev parent reply other threads:[~2014-06-10 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 11:47 Uri Sidler
2014-06-10 12:29 ` Venkat Thummala [this message]
2014-06-10 12:31 ` Venkat Thummala
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='CAF5bpL_sK5Hv26oJ-QKorBHR2Ty1YETKZS8kVB8Yhq=fsB8jRA@mail.gmail.com' \
--to=venkat.thummala.1978@gmail.com \
--cc=dev@dpdk.org \
--cc=uri.sidler@gmail.com \
/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).