From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 4D6936CC5 for ; Wed, 25 Apr 2018 15:27:01 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Apr 2018 06:26:59 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,326,1520924400"; d="scan'208";a="219278204" Received: from irsmsx154.ger.corp.intel.com ([163.33.192.96]) by orsmga005.jf.intel.com with ESMTP; 25 Apr 2018 06:26:58 -0700 Received: from irsmsx110.ger.corp.intel.com ([169.254.15.211]) by IRSMSX154.ger.corp.intel.com ([169.254.12.234]) with mapi id 14.03.0319.002; Wed, 25 Apr 2018 14:26:57 +0100 From: "Pattan, Reshma" To: "Burakov, Anatoly" , "dev@dpdk.org" CC: "Parthasarathy, JananeeX M" Thread-Topic: [PATCH v3 1/3] mem: fix 32-bit memory upper limit for non-legacy mode Thread-Index: AQHT27XAMKM7dC19ckayzn8CZVTrO6QReXrw Date: Wed, 25 Apr 2018 13:26:57 +0000 Message-ID: <3AEA2BF9852C6F48A459DA490692831F2A2C9B39@irsmsx110.ger.corp.intel.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v3 1/3] mem: fix 32-bit memory upper limit for non-legacy mode 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: , X-List-Received-Date: Wed, 25 Apr 2018 13:27:02 -0000 > -----Original Message----- > From: Burakov, Anatoly > Sent: Tuesday, April 24, 2018 11:19 AM > To: dev@dpdk.org > Cc: Pattan, Reshma ; Burakov, Anatoly > > Subject: [PATCH v3 1/3] mem: fix 32-bit memory upper limit for non-legacy > mode >=20 > 32-bit mode has an upper limit on amount of VA space it can preallocate, = but > the original implementation used the wrong constant, resulting in failure= to > initialize due to integer overflow. Fix it by using the correct constant. >=20 > Fixes: 66cc45e293ed ("mem: replace memseg with memseg lists") > Cc: anatoly.burakov@intel.com >=20 > Signed-off-by: Anatoly Burakov > --- > lib/librte_eal/common/eal_common_memory.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) >=20 Tested-by: Jananee Parthasarathy