Recently upgraded and my rig now supports 1G hugetables but no matter what I do I just cannot get the config to persist through a reboot and in all cases the standard hugetables defaults to using the 2M configuration and won't even disable transparent hugetables.
I'm pushing config to the kernel at boot time via grub which just seems to be ignored or overwritten but I just can't find out from where...
My only success thus far is to edit /etc/sysctl.conf and adding in "vm.nr_hugepages = 4096" which just applies to the defaulted 2M page sizes.
I did spot that systemd is running dev-hugepages.mount by default which I masked out as per https://www.freedesktop.org/wiki/Sof...PIFileSystems/ and replaced with my own config in /etc/fstab but still nothing.
Lastly, I have installed the hugepages package and tried applying the configuration using this which works fine but just doesn't persist through a system reboot and provides no means to making the config permanent :-?
I'll look to get further support via launchpad but before I do has anyone gotten this working that can give me some pointers?
Thanks,
K
I'm pushing config to the kernel at boot time via grub which just seems to be ignored or overwritten but I just can't find out from where...
Code:
GRUB_CMDLINE_LINUX_DEFAULT="iommu=1 amd_iommu=on default_hugepagesz=1G hugepagesz=1G hugepages=8 hugepagesz=2M hugepages=0"I did spot that systemd is running dev-hugepages.mount by default which I masked out as per https://www.freedesktop.org/wiki/Sof...PIFileSystems/ and replaced with my own config in /etc/fstab but still nothing.
Lastly, I have installed the hugepages package and tried applying the configuration using this which works fine but just doesn't persist through a system reboot and provides no means to making the config permanent :-?
I'll look to get further support via launchpad but before I do has anyone gotten this working that can give me some pointers?
Thanks,
K