From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Muhammad Zain-ul-Abideen <zain2294@gmail.com>,
Paul Emmerich <emmericp@net.in.tum.de>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] Current CONFIG_RTE_MAX_MEMSEG=256 is not enough
Date: Thu, 13 Oct 2016 17:04:15 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973CA092C3@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAN7yQ2pX=tA5N4XAGejJCkrhKjv-881ett7BESUGT3cjtnANAA@mail.gmail.com>
Hi,
> -----Original Message-----
> From: users [mailto:users-bounces@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
prev parent reply other threads:[~2016-10-13 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 14:50 Cliff Burdick
2016-10-13 14:56 ` Paul Emmerich
[not found] ` <CAN7yQ2rUyUyAw4XJcnHpq9VhF56AhgSQc4oqWoJ2FAcm+4Y+WA@mail.gmail.com>
[not found] ` <CAN7yQ2oazqOFxC-A+ipAeJTJaV2KLsAh08qD9=G++gHhVj2Arw@mail.gmail.com>
2016-10-13 17:00 ` Muhammad Zain-ul-Abideen
2016-10-13 17:04 ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D8973CA092C3@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=emmericp@net.in.tum.de \
--cc=users@dpdk.org \
--cc=zain2294@gmail.com \
/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).