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