Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
14.6. Configuring Huge Pages in Red Hat Enterprise Linux 3
Before configuring Big Pages, ensure to have read Section 14.3, “Sizing Big Pages and Huge Pages”.
In Red Hat Enterprise Linux 3 the desired size of the Huge Pages pool is specified in megabytes. The size of the pool should be configured by the incremental size of the Huge Page size. To obtain the size of Huge Pages, execute the following command:
grep Hugepagesize /proc/meminfo Hugepagesize: 2048 kB $
$ grep Hugepagesize /proc/meminfo
Hugepagesize: 2048 kB
$
The number of Huge Pages can be configured and activated by setting
hugetlb_pool in the proc file system. For example, to allocate a 1GB Huge Page pool, execute:
echo 1024 > /proc/sys/vm/hugetlb_pool
# echo 1024 > /proc/sys/vm/hugetlb_pool
Alternatively, you can use
sysctl(8) to change it:
sysctl -w vm.hugetlb_pool=1024
# sysctl -w vm.hugetlb_pool=1024
To make the change permanent, add the following line to the file
/etc/sysctl.conf. This file is used during the boot process. The Huge Pages pool is usually guaranteed if requested at boot time:
echo "vm.hugetlb_pool=1024" >> /etc/sysctl.conf
# echo "vm.hugetlb_pool=1024" >> /etc/sysctl.conf
If you allocate a large number of Huge Pages, the execution of the above commands can take a while. To verify whether the kernel was able to allocate the requested number of Huge Pages, execute:
grep HugePages_Total /proc/meminfo HugePages_Total: 512 $
$ grep HugePages_Total /proc/meminfo
HugePages_Total: 512
$
The output shows that 512 Huge Pages have been allocated. Since the size of Huge Pages on this system is 2048 KB, a Huge Page pool of 1GB has been allocated and pinned in physical memory.
If
HugePages_Total is lower than what was requested with hugetlb_pool, then the system does either not have enough memory or there are not enough physically contiguous free pages. In the latter case the system needs to be rebooted which should give you a better chance of getting the memory.
To get the number of free Huge Pages on the system, execute:
grep HugePages_Free /proc/meminfo
$ grep HugePages_Free /proc/meminfo
Free system memory will automatically be decreased by the size of the Huge Pages pool allocation regardless whether the pool is being used by an application like Oracle database or not being used:
grep MemFree /proc/meminfo
$ grep MemFree /proc/meminfo
After an Oracle database starts up, verify the Huge Pages usage. The number of free Huge Pages should decrease.
grep HugePages_Free /proc/meminfo
$ grep HugePages_Free /proc/meminfo
To free the Huge Pages pool, you can execute:
echo 0 > /proc/sys/vm/hugetlb_pool
# echo 0 > /proc/sys/vm/hugetlb_pool
This command usually takes a while to finish.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}