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 07D3DA0555; Wed, 19 Feb 2020 11:23:48 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id CEE4A4C81; Wed, 19 Feb 2020 11:23:47 +0100 (CET) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 716CC397D for ; Wed, 19 Feb 2020 11:23:46 +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 fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Feb 2020 02:23:45 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.70,459,1574150400"; d="scan'208";a="258878211" Received: from unknown (HELO [10.237.220.130]) ([10.237.220.130]) by fmsmga004.fm.intel.com with ESMTP; 19 Feb 2020 02:23:44 -0800 To: Kamaraj P Cc: dev@dpdk.org, Nageswara Rao Penumarthy , "Kamaraj P (kamp)" References: <5192f94a-e50a-7e61-2e33-a218a4b6b5b4@intel.com> From: "Burakov, Anatoly" Message-ID: <9c888eb0-2192-137c-da5c-97f30da5204a@intel.com> Date: Wed, 19 Feb 2020 10:23:44 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2 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 17-Feb-20 9:57 AM, Kamaraj P wrote: > Hi Anatoly, > Thanks for the clarifications. > > Currently we are migrating to the new DPDK 18.11 ( from 17.05).  Here is > our configuration: > ======================================================================= > We have configured the "--legacy-mem" option and changed the > CONFIG_RTE_MAX_MEM_MB to 2048 (and we are passing 2MB huge page 188 and > no 1G hugepages in the bootargs). > Our application deployment as 2G RAM > ======================================================================= > We are observing the hang issue, with above configuration. > Please see the below logs: > EAL: Detected lcore 0 as core 0 on socket 0 > EAL: Support maximum 128 logical core(s) by configuration. > EAL: Detected 1 lcore(s) > EAL: Detected 1 NUMA nodes > EAL: open shared lib /usr/lib64/librte_pmd_ixgbe.so.2.1 > EAL: open shared lib /usr/lib64/librte_pmd_e1000.so.1.1 > EAL: Multi-process socket /var/run/dpdk/rte/mp_socket > EAL: Module /sys/module/vfio_pci not found! error 2 (No such file or > directory) > EAL: VFIO PCI modules not loaded > EAL: No free hugepages reported in hugepages-1048576kB > EAL: No free hugepages reported in hugepages-1048576kB > EAL: Probing VFIO support... > EAL: Module /sys/module/vfio not found! error 2 (No such file or directory) > EAL: VFIO modules not loaded, skipping VFIO support... > EAL: Ask a virtual area of 0x2e000 bytes > EAL: Virtual area found at 0x100000000 (size = 0x2e000) > EAL: Setting up physically contiguous memory... > EAL: Setting maximum number of open files to 4096 > EAL: Detected memory type: socket_id:0 hugepage_sz:1073741824 > EAL: Detected memory type: socket_id:0 hugepage_sz:2097152 > EAL: Creating 1 segment lists: n_segs:1 socket_id:0 hugepage_sz:1073741824 > EAL: Ask a virtual area of 0x1000 bytes > EAL: Virtual area found at 0x10002e000 (size = 0x1000) > EAL: Memseg list allocated: 0x100000kB at socket 0 > EAL: Ask a virtual area of 0x40000000 bytes > <<< --- struck here ---> >>>> > > > Is there any other dpdk options thro which we can resolve the above > issue ? Any thoughts ? > Like passing the *--socket-limit* and *--m *parameter etc during the EAL > Init (could help ???). > Please suggest us. > It sounds like it hangs in eal_get_virtual_area() - we've had a similar issue before, not sure if the fix was backported to 18.11. Is this patch present in your code? http://patches.dpdk.org/patch/51943/ If not, it would be of great help if you could find the exact spot where the hang happens. -- Thanks, Anatoly