From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id CD03A2716 for ; Wed, 31 Aug 2016 21:58:39 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP; 31 Aug 2016 12:58:38 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,263,1470726000"; d="scan'208";a="1033761310" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by fmsmga001.fm.intel.com with ESMTP; 31 Aug 2016 12:58:38 -0700 Received: from fmsmsx151.amr.corp.intel.com (10.18.125.4) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.248.2; Wed, 31 Aug 2016 12:58:37 -0700 Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.149]) by FMSMSX151.amr.corp.intel.com ([169.254.7.191]) with mapi id 14.03.0248.002; Wed, 31 Aug 2016 12:58:37 -0700 From: "Wiles, Keith" To: Sarthak Ray CC: "users@dpdk.org" Thread-Topic: [dpdk-users] rte_eal_init fails with --socket-mem set to more than 192MB per socket Thread-Index: AQHSA7sl8b/+rXx5hESEAPuv9lK7+qBj8gAA Date: Wed, 31 Aug 2016 19:58:36 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.254.87.169] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <92F62697A1CF334886593EBA3F8E2BDB@intel.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] rte_eal_init fails with --socket-mem set to more than 192MB per socket X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2016 19:58:40 -0000 Regards, Keith > On Aug 31, 2016, at 2:15 PM, Sarthak Ray wrote: >=20 > Hi, >=20 > I am using dpdk-2.1.0 and I am not able to reserve memory beyond 192MB pe= r socket by using --socket-mem option. I see below error logs, though my sy= stem has enough free memory. >=20 > EAL: Not enough memory available on socket 0! Requested: 256MB, available= : 192MB > PANIC in rte_eal_init(): \Most of the time this means that contiguous memory is not available and yo= u have fragmented huge pages. The normal fix is to make sure you allocate t= he huge pages early in boot up, which to me means making sure you have the = /etc/sysctl.conf file setup with the number of huge pages. vm.nr_hugepages=3DNNN >=20 > # numactl -H > available: 2 nodes (0-1) > node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 36 37 38 39 40 4= 1 42 43 44 45 46 47 48 49 50 51 52 53 > node 0 size: 65170 MB > node 0 free: 47433 MB > node 1 cpus: 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 54 55 = 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 > node 1 size: 65536 MB > node 1 free: 49999 MB > node distances: > node 0 1 > 0: 10 21 > 1: 21 10 >=20 > Is there any max limit for reserving memory per socket? If yes, then plea= se suggest me how to increase that limit. >=20 > Thanks in advance, > Sarthak