From: Rick LaMont <lamont@dotcsw.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Segmentation fault in rte_eal_hugepage_attach
Date: Wed, 17 Dec 2014 22:54:22 -0500 [thread overview]
Message-ID: <20141218035422.GA1105@www6.g1.pair.com> (raw)
In-Reply-To: <20141217093533.GA12400@bricha3-MOBL3>
> The most likely cause of failure in mapping the memory is that the range
> requested is already used by another memory mapping in the processes address
> space. Two possible paths to look at this:
> 1) examine the /proc/<pid>/maps file for the secondary process
Brilliant advice, Bruce! This was indeed the cause. The secondary process
had some shared libraries mapped right in the middle of the viable 1G range.
The most expedient workaround was to link the primary process against those
same shared libraries, as you advised Etai here:
http://www.dpdk.info/ml/archives/dev/2014-April/001829.html
Perhaps not the most sustainable solution...
Thank you very much,
Rick LaMont | After forty years of toil
Dot C Software, Inc. | He just up and walked away
prev parent reply other threads:[~2014-12-18 3:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 4:12 Rick LaMont
2014-12-17 9:35 ` Bruce Richardson
2014-12-18 3:54 ` Rick LaMont [this message]
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=20141218035422.GA1105@www6.g1.pair.com \
--to=lamont@dotcsw.com \
--cc=bruce.richardson@intel.com \
--cc=dev@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).