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 36780A00E6 for ; Thu, 8 Aug 2019 14:37:47 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 2D3C41BE37; Thu, 8 Aug 2019 14:37:46 +0200 (CEST) Received: from mail-vk1-f195.google.com (mail-vk1-f195.google.com [209.85.221.195]) by dpdk.org (Postfix) with ESMTP id 7D8B51BE1F for ; Thu, 8 Aug 2019 14:37:44 +0200 (CEST) Received: by mail-vk1-f195.google.com with SMTP id 9so18726434vkw.4 for ; Thu, 08 Aug 2019 05:37:44 -0700 (PDT) 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=XzR/qp2Iu7zQbihpk5jXjGN0PObb2Z89kaCTrfuKS9s=; b=NKcRhSqdN3Z6CK0In+hVKhHk7IvVkNbRW5CxOkMLEdtyrAuq9cDQleInqEFzlBTZlB owKqlEgl2vXnnhEKLWuFWBnPXVQ3KPEjPd2TXXqrSUqoFOvgGokljh+BOenyhWz8jIFK lymFOV5e0UZQeJedTPV2Nu8t6/wlWjQnWXg3pj9FKTmYW3joqqmi0fUmJdtyK3nBfjb/ 8WLYmUdn/JuIGMhOv8KbTyoaDpg0g6n/7Ow0k2FZLlD8lD5vD7EJAzm9ODFNcclkNy6G iSASm4HpiYfUl0+BIFODK0PdWj18rhmWZ8WnAyD593IFRG02bzU3O0ppn2CYEMJHuF+G LM9w== X-Gm-Message-State: APjAAAX+tNOABZYh8+uqJ/n6a8nMZAYMZYXtnbwRukYwVEnG/8KklJmB tFw8SDXNXYdYkVHX48x+Sv4Jg/RB+MKrSWK6y9zvAA== X-Google-Smtp-Source: APXvYqyo9C3m2PrxQAgHj11SHrpdJ4ZM1hlLoROHOs1VFuab9WUmZy8hdKNXcvzYHOMQGoFspFOYaW4YL24qUXjghw8= X-Received: by 2002:a1f:1185:: with SMTP id 127mr5523828vkr.85.1565267863518; Thu, 08 Aug 2019 05:37:43 -0700 (PDT) MIME-Version: 1.0 References: <20190807101204.21614-1-g.singh@nxp.com> <20190808121320.12253-1-g.singh@nxp.com> In-Reply-To: <20190808121320.12253-1-g.singh@nxp.com> From: David Marchand Date: Thu, 8 Aug 2019 14:37:32 +0200 Message-ID: To: Gagandeep Singh Cc: dev , Thomas Monjalon , "Burakov, Anatoly" , Olivier Matz , Andrew Rybchenko , dpdk stable , Nipun Gupta Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v2] eal: change max hugepage sizes to 4 for ARM platforms 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 Thu, Aug 8, 2019 at 2:27 PM Gagandeep Singh wrote: > > ARM is supporting maximum 4 hugepage sizes (64K, 2M, 32M > and 1G) when granule is 4KB since very long and DPDK > support maximum 3 hugepage sizes. > > With all 4 hugepage sizes enabled, applications and some > stacks like VPP which are working over DPDK and using > "in-memory" eal option, or using separate mount points > on ARM based platform, fails at huge page initialization, > reporting error messages from eal: > > EAL: FATAL: Cannot get hugepage information. > EAL: Cannot get hugepage information. > EAL: Error - exiting with code: 1 > > This issue is visible on kernel 5.2 (stable rel), where > kernel is by default creating directories for each supported > hugepage size in /sys/kernel/mm/hugepages/ Yes, any supported hugepage size is announced in sysfs. > On earlier Stable Kernel LTR's, the directories visible in > /sys/kernel/mm/hugepages/ were dependent upon what hugepage > sizes are configured at boot time. The change is in kernel 5.0 with: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a21b0b78 where all supported sizes are now registered. > > This change increases the maximum supported mount points > to 4 for ARM based platforms. > > Cc: stable@dpdk.org > > Signed-off-by: Gagandeep Singh > Signed-off-by: Nipun Gupta > --- > > Changes in V2: > - restricted this change specific to ARM > - commit message updated > - stable added to cc Please keep me Cc:. -- David Marchand