From: Bruce Richardson <bruce.richardson@intel.com>
To: Haowei Yuan <hyuan@wustl.edu>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Problem with running the load balancer example application
Date: Sat, 20 Dec 2014 09:32:45 +0000 [thread overview]
Message-ID: <20141220093244.GA9912@bricha3-MOBL3> (raw)
In-Reply-To: <CAMctUDN2Hq0pAABUNmWh0aGT10ReykvPwKGhjqjqxHEUvfdoTA@mail.gmail.com>
On Fri, Dec 19, 2014 at 12:14:27PM -0600, Haowei Yuan wrote:
> Hi Bruce,
>
> Thank you very much for the information. I guess I will just use hugepages then.
>
> At the beginning, the reason for using the --no-huge flag was that
> somehow hugepages used by the app was not released (I don't remember
> what the exact situation was, it might be that the program failed
> somewhere because something was not properly configured), and with 2K
> hugepages, after running the app several times, there was no hugepage
> left. So I just wanted to try the --no-huge flag as it seemed to be
> easy, and I guess there are probably ways to release those hugepages.
> Then the warning messages showed up after the --no-huge flag was
> added.
>
At the end of the application run, the hugepages are released by the application
as the rest of the memory it uses is, ie. automatically on process termination.
However, the hugepage files used to map that memory are not automatically deleted.
Despite this, the memory is still available for reuse by a subsequent DPDK run - which
will automatically delete the old files on startup - or by another app - in which
case you may need to manually delete the files.
> At the moment, the app works fine with hugepages.
>
Ok, good to know.
/Bruce
> Thanks,
> Haowei
>
>
> On Fri, Dec 19, 2014 at 4:14 AM, Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> > On Fri, Dec 19, 2014 at 01:43:26AM -0600, Haowei Yuan wrote:
> >> Hi folks,
> >>
> >> I am new to DPDK and have been trying to run the load balancer example
> >> application on a machine with two NUMA nodes. Somehow the program
> >> cannot be launched correctly if I add the "--no-huge" option to the
> >> command. I am wondering if someone had seen similar problems, or maybe
> >> I did something wrong.
> >>
> >
> > Hi,
> >
> > Can I ask why you want to run the app with the -no-huge flag. That flag is
> > primarily for testing only, and is not designed for use in a real-world
> > environment.
> >
> > /Bruce
> >
prev parent reply other threads:[~2014-12-20 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 7:43 Haowei Yuan
2014-12-19 10:14 ` Bruce Richardson
[not found] ` <1f80c4cd14794b06a8f483d0fbf60b3d@BLUPR02MB115.namprd02.prod.outlook.com>
2014-12-19 18:14 ` Haowei Yuan
2014-12-20 9:32 ` Bruce Richardson [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=20141220093244.GA9912@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hyuan@wustl.edu \
/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).