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 361D2A10DA for ; Wed, 31 Jul 2019 11:15:10 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id CC2AE1B958; Wed, 31 Jul 2019 11:15:08 +0200 (CEST) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id E0E801D7 for ; Wed, 31 Jul 2019 11:15:06 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Jul 2019 02:15:06 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,329,1559545200"; d="scan'208";a="200675633" Received: from aburakov-mobl1.ger.corp.intel.com (HELO [10.237.220.92]) ([10.237.220.92]) by fmsmga002.fm.intel.com with ESMTP; 31 Jul 2019 02:15:04 -0700 To: Thomas Monjalon Cc: dev@dpdk.org References: <20190718093432.14092-1-thomas@monjalon.net> <20190730172153.29008-1-thomas@monjalon.net> From: "Burakov, Anatoly" Message-ID: <0a1c656a-9197-2060-5a28-f0fc72265651@intel.com> Date: Wed, 31 Jul 2019 10:15:04 +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: <20190730172153.29008-1-thomas@monjalon.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v3] eal: warn on legacy memory allocation requirement 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 30-Jul-19 6:21 PM, Thomas Monjalon wrote: > When using --no-huge mode, dynamic allocation is not supported. > Because of this limitation, the option --legacy-mem is implied > and -m may be needed to specify the amount of memory to allocate. > Otherwise the default amount MEMSIZE_IF_NO_HUGE_PAGE will be allocated. > > The option --socket-mem can also be used with --legacy-mem > when hugepages are supported. > > Signed-off-by: Thomas Monjalon > --- > v3: > - replace "allocation" with "amount of reserved memory" > - add --socket-mem > - more rewording > v2: > - user-oriented message > - trigger warning on any legacy mem option > --- Acked-by: Anatoly Burakov -- Thanks, Anatoly