From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by dpdk.org (Postfix) with ESMTP id 07E2E68CE for ; Mon, 2 Jun 2014 22:10:05 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3278; q=dns/txt; s=iport; t=1401739819; x=1402949419; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=08prThjbixrtbomuUI/pFVpey/Tmk6+D02imeof6MTs=; b=Mi7n7uWoSF6gv2F1F1Xg5gw/3EklUtFfn1P9jPGtyAYP8xq6XGBGQETi 7WxPEbgIls91rc0Gu/VoQBRwL07hat/cJkijeM39GoM2V/Fk1W+K8N9F9 WPGm1z0yrK45+8jCeeOJBCRo6lMIJY6UjagLvJmrqYgUKcf5n6FtKuheR E=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ag0FAHTZjFOtJV2a/2dsb2JhbABZgweBKsJZAYEVFnSCJQEBAQQnEz8MBAIBCBEEAQEfCQcyFAkIAgQOBYhCz10XjlIHBoQ6AQOaAJMtgziCLw X-IronPort-AV: E=Sophos;i="4.98,959,1392163200"; d="scan'208";a="49479492" Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-8.cisco.com with ESMTP; 02 Jun 2014 20:10:14 +0000 Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s52KAE46001979 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 2 Jun 2014 20:10:14 GMT Received: from xmb-aln-x03.cisco.com ([169.254.6.80]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Mon, 2 Jun 2014 15:10:14 -0500 From: "Niraj Sharma (nirajsha)" To: "dev@dpdk.org" Thread-Topic: l3fwd fails : Cause: Unable to create the l3fwd LPM table on socket 0 Thread-Index: AQHPfHxWw2kqAMpufEyLOOnXfoq2JpteLutA///z6IA= Date: Mon, 2 Jun 2014 20:10:14 +0000 Message-ID: References: <59AF69C657FD0841A61C55336867B5B01AA315AC@IRSMSX103.ger.corp.intel.com> In-Reply-To: <59AF69C657FD0841A61C55336867B5B01AA315AC@IRSMSX103.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.154.209.244] Content-Type: text/plain; charset="us-ascii" Content-ID: <49CCD14C1509BD40B21B59F3F20E070C@emea.cisco.com> 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 20:10:06 -0000 Bruce, Thanks for the insight. I should be able to solve this problem based on this information. Once I understand the applications, I plan to deep dive into DPDK code. -- Niraj On 6/2/14 12:01 PM, "Richardson, Bruce" wrote: > > >> -----Original Message----- >> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Niraj Sharma >>(nirajsha) >> Sent: Friday, May 30, 2014 7:59 PM >> To: dev@dpdk.org >> Subject: [dpdk-dev] l3fwd fails : Cause: Unable to create the l3fwd LPM >>table 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 >blocks, two with a single page each, i.e. 2MB in size, and the rest as a >contiguous 124MB block. > >> EAL: TSC frequency is ~3491919 KHz >> EAL: WARNING: cpu flags constant_tsc=3Dyes nonstop_tsc=3Dno -> using >>unreliable >> 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 rules are getting added to it. However, thereafter >the application is attempting to create an LPM table for IPv6 traffic and >there is not enough memory available for this. >Running a quick test on my system, the l3fwd app is requesting just over >32MB 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 only have 128MB of hugepage memory in total - and only 124MB of that >in a contiguous block, as can be seen from the statements mapping the >memory. > >Regards, >/Bruce