[dpdk-users] Current CONFIG_RTE_MAX_MEMSEG=256 is not enough

De Lara Guarch, Pablo pablo.de.lara.guarch at intel.com
Thu Oct 13 19:04:15 CEST 2016


Hi,

> -----Original Message-----
> From: users [mailto:users-bounces at dpdk.org] On Behalf Of Muhammad Zain-
> ul-Abideen
> Sent: Thursday, October 13, 2016 10:01 AM
> To: Paul Emmerich
> Cc: users
> Subject: Re: [dpdk-users] Current CONFIG_RTE_MAX_MEMSEG=256 is not
> enough
> 
> It might be a memory leakage, or unhandeled exception, because what i
> understood is that at start up it works fine but later on 2nd or 3rd
> attempt huge pages are not free, kindly see is any thread from the process
> is active, may be a zombie apocalypse.

As Paul said, it looks like memory fragmentation.
To guarantee that you won't encounter this problem again, you can reserve
the hugepages at boot time, using the kernel parameter nr_hugepages.

Pablo


More information about the users mailing list