From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 255A9B0AF for ; Mon, 2 Jun 2014 21:05:15 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 02 Jun 2014 11:59:52 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.98,958,1392192000"; d="scan'208";a="550395587" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by orsmga002.jf.intel.com with ESMTP; 02 Jun 2014 12:04:14 -0700 Received: from irsmsx152.ger.corp.intel.com (163.33.192.66) by IRSMSX101.ger.corp.intel.com (163.33.3.153) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 2 Jun 2014 20:01:36 +0100 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.58]) by IRSMSX152.ger.corp.intel.com ([169.254.6.197]) with mapi id 14.03.0123.003; Mon, 2 Jun 2014 20:01:36 +0100 From: "Richardson, Bruce" To: "Niraj Sharma (nirajsha)" , "dev@dpdk.org" Thread-Topic: l3fwd fails : Cause: Unable to create the l3fwd LPM table on socket 0 Thread-Index: AQHPfHxWw2kqAMpufEyLOOnXfoq2JpteLutA Date: Mon, 2 Jun 2014 19:01:35 +0000 Message-ID: <59AF69C657FD0841A61C55336867B5B01AA315AC@IRSMSX103.ger.corp.intel.com> References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] l3fwd fails : Cause: Unable to create the l3fwd LPM table on socket 0 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, 02 Jun 2014 19:05:16 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Niraj Sharma (nirajs= ha) > Sent: Friday, May 30, 2014 7:59 PM > To: dev@dpdk.org > Subject: [dpdk-dev] l3fwd fails : Cause: Unable to create the l3fwd LPM t= able on > socket 0 > > .... > EAL: Setting up memory... > EAL: Ask a virtual area of 0x200000 bytes > EAL: Virtual area found at 0x7f67b7800000 (size =3D 0x200000) > EAL: Ask a virtual area of 0x7c00000 bytes > EAL: Virtual area found at 0x7f67afa00000 (size =3D 0x7c00000) > EAL: Ask a virtual area of 0x200000 bytes > EAL: Virtual area found at 0x7f67af600000 (size =3D 0x200000) > EAL: Requesting 64 pages of size 2MB from socket 0 Just by way of explanation, the 64 pages are getting mapped into three bloc= ks, two with a single page each, i.e. 2MB in size, and the rest as a contig= uous 124MB block. > EAL: TSC frequency is ~3491919 KHz > EAL: WARNING: cpu flags constant_tsc=3Dyes nonstop_tsc=3Dno -> using unre= liable > clock cycles ! > EAL: Master core 0 is ready (tid=3Db86e2800) > EAL: PCI device 0000:00:03.0 on NUMA socket -1 > EAL: probe driver: 1af4:1000 rte_virtio_pmd > EAL: PCI Port IO found start=3D0xc000 with size=3D0x20 > EAL: PCI device 0000:00:04.0 on NUMA socket -1 > EAL: probe driver: 1af4:1000 rte_virtio_pmd > EAL: PCI Port IO found start=3D0xc020 with size=3D0x20 > EAL: PCI device 0000:00:05.0 on NUMA socket -1 > EAL: probe driver: 1af4:1000 rte_virtio_pmd > EAL: 0000:00:05.0 not managed by UIO driver, skipping > Initializing port 0 ... Creating queues: nb_rxq=3D1 nb_txq=3D1... > Address:00:40:47:1A:0A:44, All > ocated mbuf pool on socket 0 > LPM: Adding route 0x01010100 / 24 (0) > LPM: Adding route 0x02010100 / 24 (1) > LPM: Adding route 0x03010100 / 24 (2) > LPM: Adding route 0x04010100 / 24 (3) > LPM: Adding route 0x05010100 / 24 (4) > LPM: Adding route 0x06010100 / 24 (5) > LPM: Adding route 0x07010100 / 24 (6) > LPM: Adding route 0x08010100 / 24 (7) > LPM: LPM memory allocation failed > EAL: Error - exiting with code: 1 > Cause: Unable to create the l3fwd LPM table on socket 0 >=20 The error message indicates that you are running out of memory, or running = out of contiguous memory on your system when running the application. From = the output, it looks like the LPM table for IPv4 is getting created and 8 r= ules are getting added to it. However, thereafter the application is attemp= ting to create an LPM table for IPv6 traffic and there is not enough memory= available for this.=20 Running a quick test on my system, the l3fwd app is requesting just over 32= MB of memory for the LPM4 table and 128MB of memory for the LPM6 one. This = size of memory requests would explain the observed behaviour, given you onl= y have 128MB of hugepage memory in total - and only 124MB of that in a cont= iguous block, as can be seen from the statements mapping the memory. Regards, /Bruce