From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rick LaMont Subject: Re: Segmentation fault in rte_eal_hugepage_attach Date: Wed, 17 Dec 2014 22:54:22 -0500 Message-ID: <20141218035422.GA1105@www6.g1.pair.com> References: <20141217041236.GB15643@www6.g1.pair.com> <20141217093533.GA12400@bricha3-MOBL3> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev-VfR2kkLFssw@public.gmane.org To: Bruce Richardson Return-path: Content-Disposition: inline In-Reply-To: <20141217093533.GA12400@bricha3-MOBL3> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" > 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//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