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 6E9B6A00E6 for ; Thu, 8 Aug 2019 17:26:32 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 7F1021BE72; Thu, 8 Aug 2019 17:26:31 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id A264C1BE71; Thu, 8 Aug 2019 17:26:29 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 1470F213BD; Thu, 8 Aug 2019 11:26:29 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 08 Aug 2019 11:26:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=jpdjiiKNHkNTYjNqBlLrcf0ihfnqTE2TUiP/M2kXhyo=; b=Y3Vs0/LEo2rp UHv28f39c4nK1oPcUlq78vlljmcIeEasCU/91bWdSe6L689KgtIGHG3g0HFLw6qE IC8w/4bQdBeQ34Eh69eSnxX8kVn17boVkBZU9SQ41ZtxuHjSBHTfBkiDV6uvSHN2 YfRoIcmqpZQiZSLaX+a8YyhNZ/+II7A= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=jpdjiiKNHkNTYjNqBlLrcf0ihfnqTE2TUiP/M2kXh yo=; b=YEXwSqs0GxGbZHg0w6OxXTcQ4GslG+39OydTTsBavj+JzeRKmZPnMtllI Ks1w6DNt0ncNpkbzuwGUscMjiRCeq7mcHuf0GLEWYWo2ahI0UoIHlw2CPLtWuE+p jUkBM1xkPyB7NrsKBj96zE7We13pd/8LqBX/xVJL+TpKqeHmSFGhYP8AUeYnldNe mhwCxPTXU4hQ0j0EhFu2Z5WteFtHnfo5MpdIUdqzAye/P0ojD8+iQd5Sz9Ud0X43 pHEq4rnR7Tioq7/AUNmmbBI56XGLFrrDPCEggPxP9QO9TQ/TUbP49xrpRZ3+h5/X FIk+u88YOzTLgL/qvko+Yo+HTOAYw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudduhedgkeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuff homhgrihhnpehkvghrnhgvlhdrohhrghenucfkphepleefrddvfedruddtiedrfedunecu rfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtne cuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (31.106.23.93.rev.sfr.net [93.23.106.31]) by mail.messagingengine.com (Postfix) with ESMTPA id D91DE8005C; Thu, 8 Aug 2019 11:26:25 -0400 (EDT) From: Thomas Monjalon To: Gagandeep Singh Cc: stable@dpdk.org, David Marchand , dev , "Burakov, Anatoly" , Olivier Matz , Andrew Rybchenko , Nipun Gupta Date: Thu, 08 Aug 2019 17:26:20 +0200 Message-ID: <1653519.Tj3hMS7AGf@xps> In-Reply-To: References: <20190807101204.21614-1-g.singh@nxp.com> <20190808121320.12253-1-g.singh@nxp.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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" 08/08/2019 14:37, David Marchand: > 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 Applied with small updates in commit log (especially commit origin in 5.0), thanks.