RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Document URL: 

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Virtualization_Tuning_and_Optimization_Guide/sect-Virtualization_Tuning_Optimization_Guide-Memory-Tuning.html

Section Number and Name: 

7.2.3.2. Configuring Static Huge Pages

Describe the issue: 

Procedure 7.1. Setting huge pages reads:

"Alternatively, to make the setting persistent, use the # sysctl -w vm.nr_hugepages=N command with N being the number of huge pages. "

sysctl -w will not make a sysctl setting persistent across reboots.

Suggestions for improvement: 

The proper procedure for setting reboots persistently is to set them in /etc/sysctl.conf

# echo 'vm.nr_hugepages = X' >> /etc/sysctl.conf
# sysctl -p

Where X is the number of huge pages you want.

The setting being in /etc/sysctl.conf makes the setting load on boot. 'sysctl -p' makes the settings in /etc/sysctl.conf active when you run it.

Alternatively, huge pages can be set with a kernel argument:

hugepages=X

So you'd append the above to the GRUB_CMDLINE_LINUX= line in /etc/default/grub, back up your grub.cfg

# cp /boot/grub2/grub.cfg /boot/grub2/grub.cfg.bak

then generate a new grub2 config file

# grub2-mkconfig -o /boot/grub2/grub.cfg

Note you can use one of the two above procedures but you shouldn't use both.

Additional information: