From: E.W.Z. <kreuzerkrieg at gmail.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Questions about hugepages requiement
Date: Thu, 25 Apr 2019 20:02:45 +0300 [thread overview]
Message-ID: <5cc1e834.1c69fb81.f8db4.bdde@mx.google.com> (raw)
In-Reply-To: BYAPR11MB30473A1ED85007539A0FA37CEA3D0@BYAPR11MB3047.namprd11.prod.outlook.com
[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]
Don’t know about the minimal memory size, but here my 5 cents.
>> EAL: No free hugepages reported in hugepages-1048576Kb
As far as I remember it is just a warning, they check 1Gb pages availability, and if you opt not to use these it just gives a warning and then checks 2Mb hugepages.
>> ERROR: requested 1024 hugepages but only 672 could be allocated
To avoid this fragmentation message you can configure your boot options in GRUB to have hugepages allocated during boot
Sent from Mail for Windows 10
From: Oscar.Huang(a)microchip.com
Sent: Thursday, April 25, 2019 19:19
To: spdk(a)lists.01.org
Subject: [SPDK] Questions about hugepages requiement
Hi,
The SPDK document says "Before running an SPDK application, some hugepages must be allocated...". But at least how much is sufficient for SPDK to run?
If I give a large HUGEMEM number while run scripts/setup.sh, I could see errors like this:
# ERROR: requested 1024 hugepages but only 672 could be allocated.
# Memory might be heavily fragmented. Please try flushing the system cache, or reboot the machine.
So I usually use a much smaller HUGEMEM number, like 128, and my SPDK application can still run. But I see this message:
EAL: No free hugepages reported in hugepages-1048576Kb
What does this message imply? Is there any risk though my application can run?
It looks like scripts/setup.sh allocates 2-MB hugepages. Why does it complain about 1-GB hugepages?
Thanks
-Oscar
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
next reply other threads:[~2019-04-25 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 17:02 E.W.Z. [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-26 15:58 [SPDK] Questions about hugepages requiement Howell, Seth
2019-04-25 0:19 Oscar.Huang
2019-04-18 4:20 Lance Hartmann ORACLE
2019-04-17 0:07 Oscar.Huang
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=5cc1e834.1c69fb81.f8db4.bdde@mx.google.com \
--to=spdk@lists.01.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