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 BDCF3A0555; Wed, 19 Feb 2020 16:28:09 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 90E8C1BF78; Wed, 19 Feb 2020 16:28:09 +0100 (CET) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 60E5EB62 for ; Wed, 19 Feb 2020 16:28:08 +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 fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Feb 2020 07:28:07 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.70,459,1574150400"; d="scan'208";a="434506441" Received: from unknown (HELO [10.237.220.130]) ([10.237.220.130]) by fmsmga005.fm.intel.com with ESMTP; 19 Feb 2020 07:28:05 -0800 To: Kamaraj P Cc: Kevin Traynor , dev@dpdk.org, Nageswara Rao Penumarthy , "Kamaraj P (kamp)" , mtang2@cisco.com References: <5192f94a-e50a-7e61-2e33-a218a4b6b5b4@intel.com> <9c888eb0-2192-137c-da5c-97f30da5204a@intel.com> <56527d9f-b079-a580-4a80-2207c1822260@intel.com> From: "Burakov, Anatoly" Message-ID: Date: Wed, 19 Feb 2020 15:28:05 +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: 7bit 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 3:02 PM, Kamaraj P wrote: > Thanks for the suggestions. We didnt have --mlockall parameter option in > the rte_eal_init(). > we have just tried the option and our application says an *unrecognized > option*. > Lets us check further on this and let you know. > > Thanks, > Kamaraj > No, that's not an EAL option, that's a testpmd option. However, that's not really what i was asking. If you have a custom application, and that application called mlockall() (with appropriate flags) before EAL init, that would make all pages pinned, present and future. That means, if you mmap() anonymous memory (like EAL init does), it will take a long time because all of that memory will be pinned (and since it's 4K pages because at that point, we're not using hugepages yet, that will indeed take a long time). -- Thanks, Anatoly