From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id AE1C5A0555; Wed, 19 Feb 2020 15:23:34 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8F9B71B951; Wed, 19 Feb 2020 15:23:33 +0100 (CET) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id E32B458C4 for ; Wed, 19 Feb 2020 15:23:31 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Feb 2020 06:23:30 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.70,459,1574150400"; d="scan'208";a="434488897" Received: from unknown (HELO [10.237.220.130]) ([10.237.220.130]) by fmsmga005.fm.intel.com with ESMTP; 19 Feb 2020 06:23:28 -0800 To: Kamaraj P , Kevin Traynor Cc: dev@dpdk.org, Nageswara Rao Penumarthy , "Kamaraj P (kamp)" References: <5192f94a-e50a-7e61-2e33-a218a4b6b5b4@intel.com> <9c888eb0-2192-137c-da5c-97f30da5204a@intel.com> From: "Burakov, Anatoly" Message-ID: <56527d9f-b079-a580-4a80-2207c1822260@intel.com> Date: Wed, 19 Feb 2020 14:23:27 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] CONFIG_RTE_MAX_MEM_MB fails in DPDK18.05 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 19-Feb-20 11:16 AM, Kamaraj P wrote: > Hi Kevin/Anatoly, > > Yes we have the patch already included in our code base. > > Looks like it get struck in the below piece of the code: > mapped_addr = mmap(requested_addr, (size_t)map_sz, PROT_READ, >                                 mmap_flags, -1, 0); > > Could you please share your thoughts on this? > > Thanks, > Kamaraj > Hi, If it's stuck mapping, that probably means it is pinning the memory. Did you call mlockall() (or equivalent) before EAL initialization? -- Thanks, Anatoly