From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 0DF87592A for ; Mon, 1 Aug 2016 17:36:35 +0200 (CEST) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga101.jf.intel.com with ESMTP; 01 Aug 2016 08:36:34 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,455,1464678000"; d="scan'208";a="857313998" Received: from irsmsx151.ger.corp.intel.com ([163.33.192.59]) by orsmga003.jf.intel.com with ESMTP; 01 Aug 2016 08:36:26 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.71]) by IRSMSX151.ger.corp.intel.com ([169.254.4.15]) with mapi id 14.03.0248.002; Mon, 1 Aug 2016 16:36:25 +0100 From: "De Lara Guarch, Pablo" To: Raja Jayapal , "dev@dpdk.org" CC: Rafat Jahan , Nagaratna Patagar Thread-Topic: [dpdk-dev] l3fwd LPM memory allocation failed Thread-Index: AQHR69eenL74tpbIOEy783C/jSiqR6A0O1tA Date: Mon, 1 Aug 2016 15:36:25 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYTI4OGIxNWQtZWE4MS00NzllLTk2OTMtMTg1OGM4MTYxMWU0IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IlNsREtJSE4yQkJ3TVlaUU9zU2VSaVdUT0tPNmlDaUpHemErSlgyWlwvd1R3PSJ9 x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] l3fwd LPM memory allocation failed X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Aug 2016 15:36:37 -0000 Hi Raja, > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Raja Jayapal > Sent: Monday, August 01, 2016 2:32 AM > To: dev@dpdk.org > Cc: Rafat Jahan; Nagaratna Patagar > Subject: [dpdk-dev] l3fwd LPM memory allocation failed >=20 > Hi All, >=20 > I have installed dpdk-2.2.0 on VM and when i try to run l3fwd sample > application, facing the below memory error. >=20 > root@tcs-Standard-PC-i440FX-PIIX-1996:/home/tcs/Downloads/dpdk- > 2.2.0/examples/l3fwd# ./build/l3fwd -c 0x1 -n 1 -- -p 0x3 -- > config=3D"(0,0,0),(1,0,0)" > EAL: Detected lcore 0 as core 0 on socket 0 > EAL: Detected lcore 1 as core 0 on socket 0 > EAL: Support maximum 128 logical core(s) by configuration. > EAL: Detected 2 lcore(s) > EAL: VFIO modules not all loaded, skip VFIO support... > EAL: Setting up physically contiguous memory... > EAL: Ask a virtual area of 0x600000 bytes > EAL: Virtual area found at 0x7f2f9a800000 (size =3D 0x600000) > EAL: Ask a virtual area of 0xc00000 bytes > EAL: Virtual area found at 0x7f2f99a00000 (size =3D 0xc00000) > EAL: Ask a virtual area of 0x400000 bytes [...] > EAL: Virtual area found at 0x7f2f75200000 (size =3D 0x4600000) > EAL: Ask a virtual area of 0x600000 bytes > EAL: Virtual area found at 0x7f2f74a00000 (size =3D 0x600000) > EAL: Ask a virtual area of 0xa00000 bytes > EAL: Virtual area found at 0x7f2f73e00000 (size =3D 0xa00000) > EAL: Requesting 263 pages of size 2MB from socket 0 > EAL: TSC frequency is ~3092976 KHz > EAL: WARNING: cpu flags constant_tsc=3Dyes nonstop_tsc=3Dno -> using > unreliable clock cycles ! > EAL: Master lcore 0 is ready (tid=3D9cb32940;cpuset=3D[0]) > EAL: PCI device 0000:00:03.0 on NUMA socket -1 > EAL:=FF=FF probe driver: 8086:100e rte_em_pmd > EAL:=FF=FF PCI memory mapped at 0x7f2f9ae00000 > PMD: eth_em_dev_init(): port_id 0 vendorID=3D0x8086 deviceID=3D0x100e > EAL: PCI device 0000:00:07.0 on NUMA socket -1 > EAL:=FF=FF probe driver: 8086:100e rte_em_pmd > EAL:=FF=FF PCI memory mapped at 0x7f2f9ae20000 > PMD: eth_em_dev_init(): port_id 1 vendorID=3D0x8086 deviceID=3D0x100e > EAL: PCI device 0000:00:08.0 on NUMA socket -1 > EAL:=FF=FF probe driver: 8086:100e rte_em_pmd > EAL:=FF=FF PCI memory mapped at 0x7f2f9ae40000 > PMD: eth_em_dev_init(): port_id 2 vendorID=3D0x8086 deviceID=3D0x100e > EAL: PCI device 0000:00:09.0 on NUMA socket -1 > EAL:=FF=FF probe driver: 8086:100e rte_em_pmd > EAL:=FF=FF PCI memory mapped at 0x7f2f9ae60000 > PMD: eth_em_dev_init(): port_id 3 vendorID=3D0x8086 deviceID=3D0x100e > Initializing port 0 ... Creating queues: nb_rxq=3D1 nb_txq=3D1...=FF > Address:52:54:00:0D:AF:AF, Destination:02:00:00:00:00:00, Allocated mbuf > pool on socket 0 > LPM: Adding route 0x01010100 / 24 (0) > LPM: Adding route 0x02010100 / 24 (1) > LPM: LPM memory allocation failed > EAL: Error - exiting with code: 1 > =FF Cause: Unable to create the l3fwd LPM table on socket 0 >=20 >=20 > As mentioned in previous dpdkthreads, i tried after changing the hugepage > size to 1024 as well. > http://dpdk.org/ml/archives/dev/2014-November/007770.html > http://dpdk.org/ml/archives/users/2015-November/000066.html > echo 512 > /sys/devices/system/node/node0/hugepages/hugepages- > 2048kB/nr_hugepages > echo 1024 > /sys/devices/system/node/node0/hugepages/hugepages- > 2048kB/nr_hugepages >=20 > Tried setting the hugepage through ./tools/setup.sh (1024,4096...) as wel= l. but > facing the same error. >=20 > Could somebody help how to resolve this issue? It looks like your memory is too fragmented. Your should reboot your machin= e and reserve the hugepages as soon as possible, or even better, pass it to the k= ernel parameters, adding in grub.cfg, at the end of the rest of the parameters "hugepages=3D1= 024", to reserve 1024 pages of 2M. Btw, next time, for this kind of questions, you should use the users list u= sers@dpdk.org. Best regards, Pablo >=20 > Thanks, > Raja >=20 > =3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D > Notice: The information contained in this e-mail > message and/or attachments to it may contain > confidential or privileged information. If you are > not the intended recipient, any dissemination, use, > review, distribution, printing or copying of the > information contained in this e-mail message > and/or attachments to it are strictly prohibited. If > you have received this communication in error, > please notify us by reply e-mail or telephone and > immediately and permanently delete the message > and any attachments. Thank you >=20