DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Gregory Etelson <gregory@weka.io>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Huge ring allocation
Date: Thu, 25 Aug 2016 12:22:26 +0000	[thread overview]
Message-ID: <3F3704B6-4858-4967-960F-E5284F1B17CF@intel.com> (raw)
In-Reply-To: <9114674.mxuR5Pefat@polaris>


Regards,
Keith

> On Aug 25, 2016, at 1:05 AM, Gregory Etelson <gregory@weka.io> wrote:
> 
> Hello,
> 
> 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 allocation fails.

Another issue sometimes is huge pages are allocated after the system has booted, 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 instead of poking the value later.

vm.nr_hugepages=XXX

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

  reply	other threads:[~2016-08-25 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-25  6:05 Gregory Etelson
2016-08-25 12:22 ` Wiles, Keith [this message]
2016-08-25 12:49   ` anupam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F3704B6-4858-4967-960F-E5284F1B17CF@intel.com \
    --to=keith.wiles@intel.com \
    --cc=dev@dpdk.org \
    --cc=gregory@weka.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).