- Name
-
huge_pages - Default
-
1 - Minimum
-
0 - Maximum
-
2 - Scope
- per-stack
Control of whether huge pages are used for packet buffers:
-
0- no -
1- use huge pages if available (default) -
2- always use huge pages and fail if huge pages are not available.
Mode 1 prints syslog message if there is not enough huge pages in the system.
Mode 2 guarantees only initially-allocated packets to be in huge pages. It is recommended to use this mode together with EF_MIN_FREE_PACKETS, to control the number of such guaranteed huge pages. All non-initial packets are allocated in huge pages when possible. A syslog message is printed if the system is out of huge pages.
Non-initial packets can be allocated in non-huge pages without any warning in syslog for both
mode 1 and 2 even if the system has free huge
pages.