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 C39C1A0553; Mon, 17 Feb 2020 10:57:22 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 2D7ED1D64E; Mon, 17 Feb 2020 10:57:22 +0100 (CET) Received: from mail-wm1-f48.google.com (mail-wm1-f48.google.com [209.85.128.48]) by dpdk.org (Postfix) with ESMTP id D38571D64D for ; Mon, 17 Feb 2020 10:57:20 +0100 (CET) Received: by mail-wm1-f48.google.com with SMTP id a6so17716030wme.2 for ; Mon, 17 Feb 2020 01:57:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=m9WIQe2VtFM9OkwD53pgP0UtDOKVEop5wXBkt/xYQcA=; b=aznuMOrj/01rz7l8NpBm6kKqSAenEfBMSvEde6vovDZkb562SOkYuW06LXh7rwHETD Q2u1IKBUZadH/j4Wb7RuftsuCf9OiMe0TF1NckZoNEserx3Foe31QQ+6p3ridS53ibxu UrpOpztuf52Huqw0r0nk31Qh8TwH53QcM/7uebXcNCZmo6NPvExDAYRfsd+CmYejoVA+ RjKG/xS5JHuEu7eaHz1ycvS8P+J+4RWwfp+YK5BsgQAKVAlvZV5k8dBsLX495V2oV6WR RlZhsWR5CRlwJ22+o5YAnBn9260cLpiqCdtqlPklab7x1nXrB58vsclD4vG0WpVshI/O cFtQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=m9WIQe2VtFM9OkwD53pgP0UtDOKVEop5wXBkt/xYQcA=; b=Ms/7CT0NUzTtYxcNAfIUQ0lCv83rePIVh5/jcHnqnSj6jlwmEXWj5hrU9gD8zTBW6d rFtdoHF1YjePYlA0I4aMA0H31C1cp4O5K6Xo3ZTSFlHE4YjsBz9xxDbQa6rXMNGOQYmx nOyVZW74B77n5VoA1WIoiJRZKr3csxec183BvYq1ifyGATDXNCH/EOauzoM5/dvP9CU8 rLvqXFzAziPwfkQxIq+dc/dIATbnNrN6DvGg0hdncZl3ODIFl/JUw7O/eIdbk5My6PGB QYp0ZZeIPG4f28exKz5v8brbflQfKznk5XieSiWr7HOWMJtNlzTucpxj+74DEJG0ZKDi jyXg== X-Gm-Message-State: APjAAAWqu57XQzXOXN6p5eufd8lfNwH4FkKUpilS15hJ9DcolcQr+Pcs T1cMvr06suDToyvFJmY+uCSB/Tg5RdfabQD2cInLc7CSkko= X-Google-Smtp-Source: APXvYqw+Sw2oYYsIvUOx0COQisX5h6aVMGN6uWvMreLlW9BLDr+rBMPXFwcNq3vlCtgxzTDI4FY017/SS3s6/M1nde0= X-Received: by 2002:a05:600c:2150:: with SMTP id v16mr20927647wml.156.1581933440329; Mon, 17 Feb 2020 01:57:20 -0800 (PST) MIME-Version: 1.0 References: <5192f94a-e50a-7e61-2e33-a218a4b6b5b4@intel.com> In-Reply-To: <5192f94a-e50a-7e61-2e33-a218a4b6b5b4@intel.com> From: Kamaraj P Date: Mon, 17 Feb 2020 15:27:09 +0530 Message-ID: To: "Burakov, Anatoly" Cc: dev@dpdk.org, Nageswara Rao Penumarthy , "Kamaraj P (kamp)" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 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" 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. Thanks, Kamaraj On Tue, Dec 10, 2019 at 3:53 PM Burakov, Anatoly wrote: > 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 >