From: gyp sud <gypsud@gmail.com>
To: James Bensley <jwbensley@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] No free hugepages reported in hugepages when running DPDK helloworld example
Date: Mon, 25 Dec 2017 18:32:45 -0500 [thread overview]
Message-ID: <CAOTjYcq3v5tvxFDkEx4cK89V56iq5nHhm9VuBExb=GODSDbdKQ@mail.gmail.com> (raw)
In-Reply-To: <CAAWx_pUGaBoe22RT4QqdGgEd2sEtks7_apXDTHH+ETo3Vq05Bg@mail.gmail.com>
Thanks, James. I looked through some kernel documentation regarding
hugetlbpage support and DPDK source code (eal_hugepage_info.c in
particular), it appears the code was looking in
/sys/kernel/mm/hugepages the root huge page control directory. I
guess since my system supports both pse and pdpe1gb flag, so 2MB and
1GB pages are supported. Thus my /sys/kernel/mm/hugepages has
hugepages-1048576kB and hugepages-2048kB directories. helloworld was
searching through both directories but complained about 1GB because
I've only allocated pages for 2MB as you pointed out. So that warning
about 1GB is benign.
Cheers,
Gyp
On Sun, Dec 24, 2017 at 5:53 AM, James Bensley <jwbensley@gmail.com> wrote:
> On 23 December 2017 at 21:44, gyp sud <gypsud@gmail.com> wrote:
>> I downloaded and built dpdk-stable-16.11.4 version (using
>> x86_64-native-linuxapp-gcc target). I'm running Ubuntu 16.04.3 LTS.
>> After setting up hugepages according to http://dpdk.org/doc/quick-start or
>> http://dpdk.org/doc/guides-16.04/linux_gsg/sys_reqs.html
>>
>> mkdir -p /mnt/huge
>> mount -t hugetlbfs nodev /mnt/huge
>> echo 64 >
>> /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages
>>
>> I can see the hugepages fine.
>>
>> #cat /proc/meminfo | grep
>> HugeAnonHugePages: 284672 kB
>> ShmemHugePages: 0 kB
>> HugePages_Total: 64
>> HugePages_Free: 64
>> HugePages_Rsvd: 0
>> HugePages_Surp: 0
>> Hugepagesize: 2048 kB
>>
>> But when I run the helloWorld example, it complained about no free
>> hugepages, see below.
>>
>> #./build/helloworld -l 0-3 -n 2
>> EAL: Detected 4 lcore(s)
>> EAL: No free hugepages reported in hugepages-1048576kB
>> EAL: Probing VFIO support...
>> hello from core 1
>> hello from core 2
>> hello from core 3
>> hello from core 0
>>
>> Also, the memory info showed free hugepages were all gone.
>> #cat /proc/meminfo | grep Huge
>> AnonHugePages: 380928 kB
>> ShmemHugePages: 0 kB
>> HugePages_Total: 64
>> HugePages_Free: 0
>> HugePages_Rsvd: 0
>> HugePages_Surp: 0
>> Hugepagesize: 2048 kB
>>
>> Any idea why this is happening?
>>
>> Gyp
>
> Note the size of the HugePages in the EAL output
> "hugepages-1048576kB", you allocated 2MB HugePages, this message is
> about 1G HugePages.
>
> 1GB HugePages can only be allocated at boot up. It's "OK" though, 1GB
> HugePages aren't required, as you saw the application used the 2GB
> HugePages you allocated. For some applications and workloads that
> require lots of memory fewer 1GB pages can have a performance increase
> over more smaller 2MB HugePages.
>
> Obviously it goes without saying it's usually best to install the most
> recent DPDK version and check the most recent documentation URL, here
> you will find info about setting up 1GB HugePages if you want to do
> that:
> dpdk.org/doc/guides/linux_gsg/sys_reqs.html
>
> Cheers,
> James.
prev parent reply other threads:[~2017-12-25 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 21:44 gyp sud
2017-12-24 10:53 ` James Bensley
2017-12-25 23:32 ` gyp sud [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='CAOTjYcq3v5tvxFDkEx4cK89V56iq5nHhm9VuBExb=GODSDbdKQ@mail.gmail.com' \
--to=gypsud@gmail.com \
--cc=jwbensley@gmail.com \
--cc=users@dpdk.org \
/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).