[dpdk-users] Mempool allocation fails on first boot; but succeeds after system reboot

[Sarthak Ray]

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 at networkplumber.org>
Sent: Wednesday, August 17, 2016 9:09:48 PM
To: Sarthak Ray
Cc: users at 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 at 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