From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 79CA7C43603 for ; Tue, 10 Dec 2019 10:23:13 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id 2F8CE2073B for ; Tue, 10 Dec 2019 10:23:13 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2F8CE2073B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 0AA6A1B13C; Tue, 10 Dec 2019 11:23:12 +0100 (CET) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by dpdk.org (Postfix) with ESMTP id A8B1437A2 for ; Tue, 10 Dec 2019 11:23:09 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Dec 2019 02:23:08 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,299,1571727600"; d="scan'208";a="238064611" Received: from aburakov-mobl1.ger.corp.intel.com (HELO [10.237.220.92]) ([10.237.220.92]) by fmsmga004.fm.intel.com with ESMTP; 10 Dec 2019 02:23:07 -0800 To: Kamaraj P , dev@dpdk.org Cc: Nageswara Rao Penumarthy , "Kamaraj P (kamp)" References: From: "Burakov, Anatoly" Message-ID: <5192f94a-e50a-7e61-2e33-a218a4b6b5b4@intel.com> Date: Tue, 10 Dec 2019 10:23:06 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 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 07-Dec-19 5:01 PM, Kamaraj P wrote: > Hello All, > > Currently, we are facing an issue with memory allocation failure > in memseg_primary_init(). > When we configure the CONFIG_RTE_MAX_MEM_MB to 512MB and correspondingly > configured the number of huge pages for our platform. But the virtual > memory allocation is failing. > > It appears that its trying to allocate CONFIG_RTE_MAX_MEMSEG_PER_LIST * > Huge page size (i.e. 8192 * 2MB = 0x400000000) and virtual memory > allocation is failing. > > Also tried changing the CONFIG_RTE_MAX_MEMSEG_PER_LIST to 64 with which > virtual memory allocation is passing for the 128MB (64 * 2MB). But looks > like 128MB memory is not enough and it is causing the PCIe enumeration > failure. > Not able allocate virtual memory beyond 128MB by increasing the > CONFIG_RTE_MAX_MEMSEG_PER_LIST beyond 64. > > Is there are any settings(argument) which we need to pass as part of > rte_eal_init() > to get success in the virtual memory allocation? > Please advise. > > Thanks, > Kamaraj > I don't think there are, as the allocator wasn't designed with such memory constrained use cases in mind. You may want to try --legacy-mem option. -- Thanks, Anatoly