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 30F1FA0471 for ; Mon, 12 Aug 2019 11:42:12 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 4201E325F; Mon, 12 Aug 2019 11:42:11 +0200 (CEST) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id C5CCE1252 for ; Mon, 12 Aug 2019 11:42:09 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Aug 2019 02:42:08 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,377,1559545200"; d="scan'208";a="259725582" Received: from aburakov-mobl1.ger.corp.intel.com (HELO [10.237.220.78]) ([10.237.220.78]) by orsmga001.jf.intel.com with ESMTP; 12 Aug 2019 02:42:06 -0700 To: Hemant Agrawal , Thomas Monjalon , Gagandeep Singh Cc: David Marchand , dev , Olivier Matz , Andrew Rybchenko , Nipun Gupta References: <20190807101204.21614-1-g.singh@nxp.com> <52183700.OczlixnxyG@xps> From: "Burakov, Anatoly" Message-ID: <73c08d16-aa3c-7e82-7747-d18e8fc32ed2@intel.com> Date: Mon, 12 Aug 2019 10:42:05 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 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] [PATCH] eal: change max hugepage sizes to 4 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-Aug-19 2:28 PM, Hemant Agrawal wrote: > HI Thomas, > >>>> DPDK currently is supporting maximum 3 hugepage, sizes whereas >>>> system can support more than this e.g. >>>> 64K, 2M, 32M and 1G. >>> >>> You can mention ARM platform here, and that this issue starts with >>> kernel 5.2 (and I would try to mention this in the title as well). >>> This is better than an annotation that will be lost. >>> >>> >>>> Having these four hugepage sizes available to use by DPDK, which is >>>> valid in case of '--in-memory' EAL option or using 4 separate mount >>>> points for each hugepage size; >>>> hugepage_info_init() API reports an error. >>> >>> Can you describe what is the impact from a user point of view rather >>> than mentioning this internal function? >> >> Yes please, we need to understand how much it is critical. >> Should we Cc stable@dpdk.org for backport? >> Should it be merged at the last minute in 19.08? >> > > VPP usages in-memory option. So, VPP on ARM with kernel 5.2 wont' work without this patch. > Off-topic, but it's nice to see real-world usage for this option! -- Thanks, Anatoly