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 715B22E8F for ; Fri, 30 May 2014 14:43:54 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 30 May 2014 05:43:48 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.98,941,1392192000"; d="scan'208";a="520213114" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by orsmga001.jf.intel.com with ESMTP; 30 May 2014 05:43:47 -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; Fri, 30 May 2014 13:43:37 +0100 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.245]) by IRSMSX152.ger.corp.intel.com ([169.254.6.197]) with mapi id 14.03.0123.003; Fri, 30 May 2014 13:43:37 +0100 From: "Burakov, Anatoly" To: Kypriotis Angelos , "dev@dpdk.org" Thread-Topic: [dpdk-dev] buffer allocation failure in NUMA platform Thread-Index: AQHPe/y84IFxeB5hgUmzIqvXwhLS5JtZEMXQ Date: Fri, 30 May 2014 12:43:37 +0000 Message-ID: References: <53886F51.6060807@nsn.com> In-Reply-To: <53886F51.6060807@nsn.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] buffer allocation failure in NUMA platform 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, 30 May 2014 12:43:54 -0000 Hi Kypriotis, > cat /sys/devices/system/node/node1/hugepages/hugepages- > 2048kB/nr_hugepages > --> 1024 > cat /sys/devices/system/node/node0/hugepages/hugepages- > 2048kB/nr_hugepages > --> 1024 >=20 > When I try to pin my process to specific nodes like this : >=20 > numactl --physcpubind=3D12-15 -- ./my_simulator -c f000 -n 2 -b > 0000:01:00.0 --socket-mem=3D0,2048 -- my_simulator.conf , >=20 > I get 'RING:cannot reserve memory' error. Here is the relevant part : >=20 > EAL: Setting up memory... > EAL: Ask a virtual area of 0x1200000 bytes > EAL: Virtual area found at 0x7f217a600000 (size =3D 0x1200000) > EAL: Ask a virtual area of 0x3ec00000 bytes > EAL: Virtual area found at 0x7f213b800000 (size =3D 0x3ec00000) > EAL: Ask a virtual area of 0x200000 bytes > EAL: Virtual area found at 0x7f213b400000 (size =3D 0x200000) > EAL: Ask a virtual area of 0x3fc00000 bytes > EAL: Virtual area found at 0x7f20fb600000 (size =3D 0x3fc00000) > EAL: Ask a virtual area of 0x200000 bytes > EAL: Virtual area found at 0x7f20fb200000 (size =3D 0x200000) > EAL: Ask a virtual area of 0x200000 bytes > EAL: Virtual area found at 0x7f20fae00000 (size =3D 0x200000) > EAL: Ask a virtual area of 0x7fc00000 bytes > EAL: Virtual area found at 0x7f207b000000 (size =3D 0x7fc00000) > EAL: Ask a virtual area of 0x200000 bytes > EAL: Virtual area found at 0x7f207ac00000 (size =3D 0x200000) > EAL: Ask a virtual area of 0x200000 bytes > EAL: Virtual area found at 0x7f207a800000 (size =3D 0x200000) > EAL: Requesting 1024 pages of size 2MB from socket 1 > EAL: TSC frequency is ~1600000 KHz > EAL: Master core 12 is ready (tid=3D81c69840) > EAL: Core 13 is ready (tid=3D7fd55700) > EAL: Core 15 is ready (tid=3D7ed53700) > EAL: Core 14 is ready (tid=3D7f554700) > RING: Cannot reserve memory > Failed to allocate packet buffer pool. >=20 > If I do not use --socket-mem=3D0,2048 memory ( 1024 pages ) is requested > from both sockets 0 and 1 and it works, but I want to use node 1 only. >=20 > In addition in order to request for 1024 pages in node 1 I must pass the = -- > socket-mem parameter as above. I would expect that what I should pass is= -- > socket-mem=3D0,1024, but then the actual memory requested is 512. Am I > missing something here or is it a bug? This is by design. If you want memory from specific socket, use --socket-me= m. The "512" number you get is the number of pages. Each page is 2MB in siz= e, so that amounts to 512 * 2MB =3D=3D 1024MB requested, just as you specif= ied on your command-line. Best regards, Anatoly Burakov DPDK SW Engineer