Enabling Hugepages at boot time on centos 7
I am trying to enable hugepages for use with ovs and DPDK on centos 7. I have tried to edit the GRUB_CMDLINE_LINUX in /etc/default/grub see code below. GRUB_CMDLINE_LINUX="crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet hugepagesz=1G hugepages=16 hugepagesz=2M hugepages=2048 iommu=pt intel_iommu=on isolcpus=1-13,15-27"
grub2-mkconfig -o /boot/grub2/grub.cfg :
However after i reboot and issue the cat /proc/cmdline, the resulting output does not show appended hugepage entries. :-(
[root@localhost ~]# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.10.0-327.36.3.el7.x86_64 root=/dev/mapper/centos-
root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb
quiet LANG=en_GB.UTF-8
[root@localhost ~]# grep Huge /proc/meminfo :
Am i missing anything please?
centos grub2 virtual-machine grub
edited Nov 20 at 22:19
Rui F Ribeiro
38.9k1479129
asked Dec 15 '16 at 16:57
esigenesis
63
bumped to the homepage by Community♦ 57 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am trying to enable hugepages for use with ovs and DPDK on centos 7. I have tried to edit the GRUB_CMDLINE_LINUX in /etc/default/grub see code below. GRUB_CMDLINE_LINUX="crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet hugepagesz=1G hugepages=16 hugepagesz=2M hugepages=2048 iommu=pt intel_iommu=on isolcpus=1-13,15-27"
grub2-mkconfig -o /boot/grub2/grub.cfg :
However after i reboot and issue the cat /proc/cmdline, the resulting output does not show appended hugepage entries. :-(
[root@localhost ~]# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.10.0-327.36.3.el7.x86_64 root=/dev/mapper/centos-
root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb
quiet LANG=en_GB.UTF-8
[root@localhost ~]# grep Huge /proc/meminfo :
Am i missing anything please?
centos grub2 virtual-machine grub
edited Nov 20 at 22:19
Rui F Ribeiro
38.9k1479129
asked Dec 15 '16 at 16:57
esigenesis
63
bumped to the homepage by Community♦ 57 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
(A random troubleshooting step): Did the change make it to/boot/grub2/grub.cfg? (that's a plain text file, uselessor your favorite editor to check)
– derobert
Dec 15 '16 at 17:57
Hi @derobert thanks for the useful tip. the changes actually made it to /boot/grub2/grub.cfg. See output here **** linuxefi /vmlinuz-3.10.0-327.36.3.el7.x86_64 root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet hugepagesz=1G hugepages=16 hugepagesz=2M hugepages=2048 iommu=pt intel_iommu=on isolcpus=1-13,15-27**** I am not sure why the hugepage values still come up with zero values after rebooting. Thanks
– esigenesis
Dec 19 '16 at 15:48
add a comment |
I am trying to enable hugepages for use with ovs and DPDK on centos 7. I have tried to edit the GRUB_CMDLINE_LINUX in /etc/default/grub see code below. GRUB_CMDLINE_LINUX="crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet hugepagesz=1G hugepages=16 hugepagesz=2M hugepages=2048 iommu=pt intel_iommu=on isolcpus=1-13,15-27"
grub2-mkconfig -o /boot/grub2/grub.cfg :
However after i reboot and issue the cat /proc/cmdline, the resulting output does not show appended hugepage entries. :-(
[root@localhost ~]# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.10.0-327.36.3.el7.x86_64 root=/dev/mapper/centos-
root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb
quiet LANG=en_GB.UTF-8
[root@localhost ~]# grep Huge /proc/meminfo :
Am i missing anything please?
centos grub2 virtual-machine grub
edited Nov 20 at 22:19
Rui F Ribeiro
38.9k1479129
asked Dec 15 '16 at 16:57
esigenesis
63
I am trying to enable hugepages for use with ovs and DPDK on centos 7. I have tried to edit the GRUB_CMDLINE_LINUX in /etc/default/grub see code below. GRUB_CMDLINE_LINUX="crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet hugepagesz=1G hugepages=16 hugepagesz=2M hugepages=2048 iommu=pt intel_iommu=on isolcpus=1-13,15-27"
grub2-mkconfig -o /boot/grub2/grub.cfg :
However after i reboot and issue the cat /proc/cmdline, the resulting output does not show appended hugepage entries. :-(
[root@localhost ~]# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.10.0-327.36.3.el7.x86_64 root=/dev/mapper/centos-
root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb
quiet LANG=en_GB.UTF-8
[root@localhost ~]# grep Huge /proc/meminfo :
Am i missing anything please?
centos grub2 virtual-machine grub
centos grub2 virtual-machine grub
edited Nov 20 at 22:19
Rui F Ribeiro
38.9k1479129
asked Dec 15 '16 at 16:57
esigenesis
63
edited Nov 20 at 22:19
Rui F Ribeiro
38.9k1479129
asked Dec 15 '16 at 16:57
esigenesis
63
edited Nov 20 at 22:19
Rui F Ribeiro
38.9k1479129
edited Nov 20 at 22:19
Rui F Ribeiro
38.9k1479129
edited Nov 20 at 22:19
Rui F Ribeiro
38.9k1479129
38.9k1479129
asked Dec 15 '16 at 16:57
esigenesis
63
asked Dec 15 '16 at 16:57
esigenesis
63
asked Dec 15 '16 at 16:57
esigenesis
63
63
bumped to the homepage by Community♦ 57 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 57 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
(A random troubleshooting step): Did the change make it to/boot/grub2/grub.cfg? (that's a plain text file, uselessor your favorite editor to check)
– derobert
Dec 15 '16 at 17:57
Hi @derobert thanks for the useful tip. the changes actually made it to /boot/grub2/grub.cfg. See output here **** linuxefi /vmlinuz-3.10.0-327.36.3.el7.x86_64 root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet hugepagesz=1G hugepages=16 hugepagesz=2M hugepages=2048 iommu=pt intel_iommu=on isolcpus=1-13,15-27**** I am not sure why the hugepage values still come up with zero values after rebooting. Thanks
– esigenesis
Dec 19 '16 at 15:48
add a comment |
(A random troubleshooting step): Did the change make it to/boot/grub2/grub.cfg? (that's a plain text file, uselessor your favorite editor to check)
– derobert
Dec 15 '16 at 17:57
Hi @derobert thanks for the useful tip. the changes actually made it to /boot/grub2/grub.cfg. See output here **** linuxefi /vmlinuz-3.10.0-327.36.3.el7.x86_64 root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet hugepagesz=1G hugepages=16 hugepagesz=2M hugepages=2048 iommu=pt intel_iommu=on isolcpus=1-13,15-27**** I am not sure why the hugepage values still come up with zero values after rebooting. Thanks
– esigenesis
Dec 19 '16 at 15:48
(A random troubleshooting step): Did the change make it to
/boot/grub2/grub.cfg? (that's a plain text file, use less or your favorite editor to check)– derobert
Dec 15 '16 at 17:57
(A random troubleshooting step): Did the change make it to
/boot/grub2/grub.cfg? (that's a plain text file, use less or your favorite editor to check)– derobert
Dec 15 '16 at 17:57
Hi @derobert thanks for the useful tip. the changes actually made it to /boot/grub2/grub.cfg. See output here **** linuxefi /vmlinuz-3.10.0-327.36.3.el7.x86_64 root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet hugepagesz=1G hugepages=16 hugepagesz=2M hugepages=2048 iommu=pt intel_iommu=on isolcpus=1-13,15-27**** I am not sure why the hugepage values still come up with zero values after rebooting. Thanks
– esigenesis
Dec 19 '16 at 15:48
Hi @derobert thanks for the useful tip. the changes actually made it to /boot/grub2/grub.cfg. See output here **** linuxefi /vmlinuz-3.10.0-327.36.3.el7.x86_64 root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet hugepagesz=1G hugepages=16 hugepagesz=2M hugepages=2048 iommu=pt intel_iommu=on isolcpus=1-13,15-27**** I am not sure why the hugepage values still come up with zero values after rebooting. Thanks
– esigenesis
Dec 19 '16 at 15:48
add a comment |
1 Answer
1
active
oldest
votes
I was dealing with the same thing on CentOS 7.4.
Two things I noticed in your case:
You have two entries for
hugepagesz(1G and 2M) andhugepage(16 and 2048). I'm not sure whether you can do that.
I generated the config file into /etc/grub2.cfg before reboot:
grub2-mkconfig -o /etc/grub2.cfg
In my case, GRUB_CMDLINE_LINUX in /etc/default/grub has the following value (50 1G pages):
GRUB_CMDLINE_LINUX="rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet intel_iommu=on isolcpus=1,2,3,4,5,6,7,8,9,10,11 default_hugepagesz=1G hugepagesz=1G hugepages=50"
Also check whether your kernel has required options enabled (see DPDK manual, section 2.3.1 for these):
grep <OPTION>= /boot/config-`uname -r`
And check whether your CPU supports 1GB pages (searching for pdpe1gb cpu flag):
grep pdpe1gb /proc/cpuinfo
EDIT: Also check whether you mounted the memory properly (see DPDK manual, section 2.3.2.2).
answered Jan 17 at 12:31
kubouch
11
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f330669%2fenabling-hugepages-at-boot-time-on-centos-7%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I was dealing with the same thing on CentOS 7.4.
Two things I noticed in your case:
You have two entries for
hugepagesz(1G and 2M) andhugepage(16 and 2048). I'm not sure whether you can do that.
I generated the config file into /etc/grub2.cfg before reboot:
grub2-mkconfig -o /etc/grub2.cfg
In my case, GRUB_CMDLINE_LINUX in /etc/default/grub has the following value (50 1G pages):
GRUB_CMDLINE_LINUX="rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet intel_iommu=on isolcpus=1,2,3,4,5,6,7,8,9,10,11 default_hugepagesz=1G hugepagesz=1G hugepages=50"
Also check whether your kernel has required options enabled (see DPDK manual, section 2.3.1 for these):
grep <OPTION>= /boot/config-`uname -r`
And check whether your CPU supports 1GB pages (searching for pdpe1gb cpu flag):
grep pdpe1gb /proc/cpuinfo
EDIT: Also check whether you mounted the memory properly (see DPDK manual, section 2.3.2.2).
answered Jan 17 at 12:31
kubouch
11
add a comment |
I was dealing with the same thing on CentOS 7.4.
Two things I noticed in your case:
You have two entries for
hugepagesz(1G and 2M) andhugepage(16 and 2048). I'm not sure whether you can do that.
I generated the config file into /etc/grub2.cfg before reboot:
grub2-mkconfig -o /etc/grub2.cfg
In my case, GRUB_CMDLINE_LINUX in /etc/default/grub has the following value (50 1G pages):
GRUB_CMDLINE_LINUX="rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet intel_iommu=on isolcpus=1,2,3,4,5,6,7,8,9,10,11 default_hugepagesz=1G hugepagesz=1G hugepages=50"
Also check whether your kernel has required options enabled (see DPDK manual, section 2.3.1 for these):
grep <OPTION>= /boot/config-`uname -r`
And check whether your CPU supports 1GB pages (searching for pdpe1gb cpu flag):
grep pdpe1gb /proc/cpuinfo
EDIT: Also check whether you mounted the memory properly (see DPDK manual, section 2.3.2.2).
answered Jan 17 at 12:31
kubouch
11
add a comment |
I was dealing with the same thing on CentOS 7.4.
Two things I noticed in your case:
You have two entries for
hugepagesz(1G and 2M) andhugepage(16 and 2048). I'm not sure whether you can do that.
I generated the config file into /etc/grub2.cfg before reboot:
grub2-mkconfig -o /etc/grub2.cfg
In my case, GRUB_CMDLINE_LINUX in /etc/default/grub has the following value (50 1G pages):
GRUB_CMDLINE_LINUX="rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet intel_iommu=on isolcpus=1,2,3,4,5,6,7,8,9,10,11 default_hugepagesz=1G hugepagesz=1G hugepages=50"
Also check whether your kernel has required options enabled (see DPDK manual, section 2.3.1 for these):
grep <OPTION>= /boot/config-`uname -r`
And check whether your CPU supports 1GB pages (searching for pdpe1gb cpu flag):
grep pdpe1gb /proc/cpuinfo
EDIT: Also check whether you mounted the memory properly (see DPDK manual, section 2.3.2.2).
answered Jan 17 at 12:31
kubouch
11
I was dealing with the same thing on CentOS 7.4.
Two things I noticed in your case:
You have two entries for
hugepagesz(1G and 2M) andhugepage(16 and 2048). I'm not sure whether you can do that.
I generated the config file into /etc/grub2.cfg before reboot:
grub2-mkconfig -o /etc/grub2.cfg
In my case, GRUB_CMDLINE_LINUX in /etc/default/grub has the following value (50 1G pages):
GRUB_CMDLINE_LINUX="rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet intel_iommu=on isolcpus=1,2,3,4,5,6,7,8,9,10,11 default_hugepagesz=1G hugepagesz=1G hugepages=50"
Also check whether your kernel has required options enabled (see DPDK manual, section 2.3.1 for these):
grep <OPTION>= /boot/config-`uname -r`
And check whether your CPU supports 1GB pages (searching for pdpe1gb cpu flag):
grep pdpe1gb /proc/cpuinfo
EDIT: Also check whether you mounted the memory properly (see DPDK manual, section 2.3.2.2).
answered Jan 17 at 12:31
kubouch
11
edited Jan 17 at 12:36
answered Jan 17 at 12:31
kubouch
11
answered Jan 17 at 12:31
kubouch
11
answered Jan 17 at 12:31
kubouch
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f330669%2fenabling-hugepages-at-boot-time-on-centos-7%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
(A random troubleshooting step): Did the change make it to
/boot/grub2/grub.cfg? (that's a plain text file, uselessor your favorite editor to check)– derobert
Dec 15 '16 at 17:57
Hi @derobert thanks for the useful tip. the changes actually made it to /boot/grub2/grub.cfg. See output here **** linuxefi /vmlinuz-3.10.0-327.36.3.el7.x86_64 root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet hugepagesz=1G hugepages=16 hugepagesz=2M hugepages=2048 iommu=pt intel_iommu=on isolcpus=1-13,15-27**** I am not sure why the hugepage values still come up with zero values after rebooting. Thanks
– esigenesis
Dec 19 '16 at 15:48