From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <keith.wiles@intel.com>
Received: from mga01.intel.com (mga01.intel.com [192.55.52.88])
 by dpdk.org (Postfix) with ESMTP id D5D14558B
 for <dev@dpdk.org>; Thu, 25 Aug 2016 14:22:33 +0200 (CEST)
Received: from orsmga001.jf.intel.com ([10.7.209.18])
 by fmsmga101.fm.intel.com with ESMTP; 25 Aug 2016 05:22:28 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.28,575,1464678000"; d="scan'208";a="1020160054"
Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201])
 by orsmga001.jf.intel.com with ESMTP; 25 Aug 2016 05:22:27 -0700
Received: from fmsmsx112.amr.corp.intel.com (10.18.116.6) by
 FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Thu, 25 Aug 2016 05:22:27 -0700
Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.149]) by
 FMSMSX112.amr.corp.intel.com ([169.254.5.33]) with mapi id 14.03.0248.002;
 Thu, 25 Aug 2016 05:22:27 -0700
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Gregory Etelson <gregory@weka.io>
CC: "dev@dpdk.org" <dev@dpdk.org>
Thread-Topic: [dpdk-dev] Huge ring allocation
Thread-Index: AQHR/pbWG3DHDc4kFUe4J36SezUZz6BaDteA
Date: Thu, 25 Aug 2016 12:22:26 +0000
Message-ID: <3F3704B6-4858-4967-960F-E5284F1B17CF@intel.com>
References: <9114674.mxuR5Pefat@polaris>
In-Reply-To: <9114674.mxuR5Pefat@polaris>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.254.37.240]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <899CC655BA8B2748ABD28E3DCA752414@intel.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dpdk-dev] Huge ring allocation
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2016 12:22:34 -0000


Regards,
Keith

> On Aug 25, 2016, at 1:05 AM, Gregory Etelson <gregory@weka.io> wrote:
>=20
> Hello,
>=20
> I have a DPDK process that creates pktmbuf pool with 2_000_000 objects
> In CentOS 6.x x86-64, ring size of this pool is 16MB
> 8 2MB hugepages required to hold such ring.

Have you try to use 1G huge pages, is that an option?

> In some cases, hugepages are too fragmented and there are no 8 contiguous=
 hugepages for the ring.
> As the result, the process has enough hugepages memory, but ring allocati=
on fails.

Another issue sometimes is huge pages are allocated after the system has bo=
oted, which means you need to assign the number of huge pages very early in=
 the boot process. This means adding a line in the sysctrl.conf file instea=
d of poking the value later.

vm.nr_hugepages=3DXXX

> I use a workaround for these cases and create a ring with standard OS all=
ocation routines.
> Is there another way I could use unclaimed dpdk hugepages for that alloca=
tion ?
>=20
> Regards,
> Gregory