From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 36DBF2C60 for ; Fri, 26 Feb 2016 11:59:39 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 26 Feb 2016 02:59:38 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,498,1449561600"; d="scan'208";a="924411510" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by fmsmga002.fm.intel.com with ESMTP; 26 Feb 2016 02:59:37 -0800 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.237]) by IRSMSX104.ger.corp.intel.com ([169.254.5.87]) with mapi id 14.03.0248.002; Fri, 26 Feb 2016 10:53:10 +0000 From: "Ananyev, Konstantin" To: "Rapelly, Varun" , "dev@dpdk.org" Thread-Topic: ACL memory allocation failures Thread-Index: AdFwf4kdB1whTVNNQG6hirscCjj/gAAANPTAAADEVXA= Date: Fri, 26 Feb 2016 10:53:09 +0000 Message-ID: <2601191342CEEE43887BDE71AB97725836B0BA25@irsmsx105.ger.corp.intel.com> References: In-Reply-To: Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMjVjMDc0NDgtNmE1My00NDM4LTllOWYtNGY1OGFhMDBiNDUzIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6InBDNTdsdnBjejJrYmtEOHZRNkE5b1IxaUNmZ0RVeXZFMWJJZTNxb2xhaEE9In0= x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] ACL memory allocation failures 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: Fri, 26 Feb 2016 10:59:39 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Rapelly, Varun > Sent: Friday, February 26, 2016 10:28 AM > To: dev@dpdk.org > Subject: Re: [dpdk-dev] ACL memory allocation failures >=20 > Hi All, >=20 > When I'm trying to configure some 5000+ ACL rules with different source I= P addresses, getting ACL memory allocation failure. I'm using > DPDK 2.1. >=20 > [root@ACLISSUE log_2015_10_26_08_19_42]# vim np.log > match nodes/bytes used: 816/104448 > total: 12940832 bytes > ACL: Build phase for ACL "ipv4_acl_table2": > memory consumed: 947913495 > ACL: trie 0: number of rules: 816 > ACL: allocation of 12966528 bytes on socket 0 for ipv4_acl_table1 failed > ACL: Build phase for ACL "ipv4_acl_table1": > memory consumed: 947913495 > ACL: trie 0: number of rules: 817 > EAL: Error - exiting with code: 1 > Cause: Failed to build ACL trie >=20 > Again sourced the ACL config file. After adding around 77 again the same = error came. >=20 > total: 14912784 bytes > ACL: Build phase for ACL "ipv4_acl_table1": > memory consumed: 1040188260 > ACL: trie 0: number of rules: 893 > ACL: allocation of 14938480 bytes on socket 0 for ipv4_acl_table2 failed You are running out of hugepages memory. > ACL: Build phase for ACL "ipv4_acl_table2": > memory consumed: 1040188260 > ACL: trie 0: number of rules: 894 > EAL: Error - exiting with code: 1 > Cause: Failed to build ACL trie >=20 > Where to increase the memory to avoid this issue? Refer to: http://dpdk.org/doc/guides/linux_gsg/sys_reqs.html#running-dpdk-application= s Section 2.3.2=20 Konstantin