DPDK usage discussions
 help / color / mirror / Atom feed
From: Sarthak Ray <sarthak_ray@outlook.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Mempool allocation fails on first boot; but succeeds after system reboot
Date: Thu, 18 Aug 2016 13:42:18 +0000	[thread overview]
Message-ID: <MAXPR01MB0315E3AE1FE81889AE4906399F150@MAXPR01MB0315.INDPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20160817083948.5024edec@xeon-e3>

Thanks Stephen for your quick response.


My dpdk application uses 2MB hugepages; but I was reserving 1GB hugepages during bootup. Corrected the same and now it is working fine.


Thanks again,

Sarthak

________________________________
From: Stephen Hemminger <stephen@networkplumber.org>
Sent: Wednesday, August 17, 2016 9:09:48 PM
To: Sarthak Ray
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Mempool allocation fails on first boot; but succeeds after system reboot

On Wed, 17 Aug 2016 13:10:35 +0000
Sarthak Ray <sarthak_ray@outlook.com> wrote:

> Hi,
>
> I am using dpdk-2.1.0 for a platform appliance, where I am facing issue with mempool allocation.
>
> On the firstboot of the newly installed appliance, my dpdk application is not coming up saying failure in mbuf allocation on socket 0. But once I reboot the system, it comes up without any issues.

How big is the huge page memory on the system?
On initial boot, the free memory is usually contiguous after a lot of programs
run it gets fragmented.  You can configure grub command line to reserve huge pages
before userspace starts; see kernel documentation Documentation/vm/hugepages.txt

      reply	other threads:[~2016-08-18 13:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17 13:10 Sarthak Ray
2016-08-17 15:39 ` Stephen Hemminger
2016-08-18 13:42   ` Sarthak Ray [this message]

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=MAXPR01MB0315E3AE1FE81889AE4906399F150@MAXPR01MB0315.INDPRD01.PROD.OUTLOOK.COM \
    --to=sarthak_ray@outlook.com \
    --cc=stephen@networkplumber.org \
    --cc=users@dpdk.org \
    /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).