From: anupam <anupam.kapoor@gmail.com>
To: Gregory Etelson <gregory@weka.io>
Cc: "Wiles\, Keith" <keith.wiles@intel.com>, "dev\@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Huge ring allocation
Date: Thu, 25 Aug 2016 18:19:42 +0530 [thread overview]
Message-ID: <8737lt813t.fsf@fatcat.parallelwireless> (raw)
In-Reply-To: <3F3704B6-4858-4967-960F-E5284F1B17CF@intel.com>
>>>>> [2016-08-25T17:52:26+0530]: "Keith Wiles" (keith-wiles):
,----[ keith-wiles ]
| Another issue sometimes is huge pages are allocated after the system
| has booted, which means you need to assign the number of huge pages very
| early in the boot process. This means adding a line in the sysctrl.conf
| file instead of poking the value later.
|
| vm.nr_hugepages=XXX
`----
you might also try passing 'hugepages' option as kernel command line
parameters e.g.
'... hugepages=N '
from linux-kernel's Documentation/vm/hugetlbpage.txt we have the
following
,----[Documentation/vm/hugetlbpage.txt:69]
| The administrator can allocate persistent huge pages on the kernel boot
| command line by specifying the "hugepages=N" parameter, where 'N' = the
| number of huge pages requested. This is the most reliable method of
| allocating huge pages as memory has not yet become fragmented.
`----
---
thanks
anupam
prev parent reply other threads:[~2016-08-25 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 6:05 Gregory Etelson
2016-08-25 12:22 ` Wiles, Keith
2016-08-25 12:49 ` anupam [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=8737lt813t.fsf@fatcat.parallelwireless \
--to=anupam.kapoor@gmail.com \
--cc=dev@dpdk.org \
--cc=gregory@weka.io \
--cc=keith.wiles@intel.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).