From: "Zhang, Jerry" <jerry.zhang@intel.com>
To: Anand S Angadi <as.anand@globaledgesoft.com>,
Matthew Hall <mhall@mhcomputing.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] reg : adding grub entry with hugepages.
Date: Mon, 1 Sep 2014 09:39:28 +0000 [thread overview]
Message-ID: <FA09AAB07F084C4DA208D537E2734D2C374A28D7@CDSMSX102.ccr.corp.intel.com> (raw)
In-Reply-To: <54043BCB.1040304@globaledgesoft.com>
>-----Original Message-----
>From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Anand S Angadi
>Sent: Monday, September 1, 2014 5:27 PM
>To: Matthew Hall
>Cc: dev@dpdk.org
>Subject: Re: [dpdk-dev] reg : adding grub entry with hugepages.
>
>On 09/01/2014 02:36 PM, Matthew Hall wrote:
>> On Mon, Sep 01, 2014 at 02:32:40PM +0530, Anand S Angadi wrote:
>>>> Hello everyone,
>>>> I am using fedora 16, i want to Add additional Grub entry with hugepages
>enabled permanently can u tell me how can i add?
>>>> and wher can i add?
>> Try /etc/default/grub .
>>
>Hi Matthew,
>I added "default_hugepagesz=2M hugepagesz=2M hugepages=1024" and did
>reboot.
>after i did cat /proc/meminfo but i am not getting Hugepages_total 1024.
>the output is as mentioned bellow.
>
>$cat /proc/meminfo
>:
>:
>:
>HardwareCorrupted: 0 kB
>AnonHugePages: 43008 kB
>HugePages_Total: 0
>HugePages_Free: 0
>HugePages_Rsvd: 0
>HugePages_Surp: 0
>Hugepagesize: 2048 kB
>DirectMap4k: 12288 kB
>DirectMap2M: 4024320 kB
>$
>
Make sure current kernel parameters is correct by below command.
$cat /proc/cmdline
next prev parent reply other threads:[~2014-09-01 9:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54040572.5090002@globaledgesoft.com>
2014-09-01 8:44 ` Anand S Angadi
2014-09-01 8:52 ` Zhang, Jerry
2014-09-01 9:02 ` Anand S Angadi
2014-09-01 9:06 ` Matthew Hall
2014-09-01 9:19 ` Richardson, Bruce
2014-09-01 9:26 ` Anand S Angadi
2014-09-01 9:39 ` Zhang, Jerry [this message]
2014-09-01 9:36 ` Zhang, Jerry
2014-09-01 9:57 ` Richardson, Bruce
2014-09-01 9:22 ` Richardson, Bruce
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=FA09AAB07F084C4DA208D537E2734D2C374A28D7@CDSMSX102.ccr.corp.intel.com \
--to=jerry.zhang@intel.com \
--cc=as.anand@globaledgesoft.com \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/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).