With CONFIG_HUGETLBFS:

$ sudo dmesg | grep -i huge
[    0.140447] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.140496] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[    0.140522] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.140546] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[   10.532665] systemd[1]: Mounting Huge Pages File System...
[   10.801024] systemd[1]: Mounted Huge Pages File System.


** Description changed:

  [Impact]
  
  Huge pages can't be managed via hugeadm which requires hugetlbfs.
  
  [Test Case]
  
  $ hugeadm --pool-list
  hugeadm:ERROR: kernel does not support huge pages
  
  [Fix]
  
  Enable CONFIG_HUGETLBFS
  
  [Regression Potential]
  
- TBD.
+ This config enables code that is disabled by default. However, there is
+ minimal stub code running at boot so problems would most likely show up
+ as splats during boot.

** Description changed:

  [Impact]
  
  Huge pages can't be managed via hugeadm which requires hugetlbfs.
  
  [Test Case]
  
  $ hugeadm --pool-list
  hugeadm:ERROR: kernel does not support huge pages
  
  [Fix]
  
  Enable CONFIG_HUGETLBFS
  
  [Regression Potential]
  
  This config enables code that is disabled by default. However, there is
  minimal stub code running at boot so problems would most likely show up
- as splats during boot.
+ as splats during boot or later when hugetlbfs is explicitly turned on.

** Description changed:

  [Impact]
  
  Huge pages can't be managed via hugeadm which requires hugetlbfs.
  
  [Test Case]
  
  $ hugeadm --pool-list
  hugeadm:ERROR: kernel does not support huge pages
+ 
+ With fix:
+ $ hugeadm --pool-list
+       Size  Minimum  Current  Maximum  Default
+      65536        0        0        0         
+    2097152        0        0        0        *
+   33554432        0        0        0         
+ 1073741824        0        0        0         
  
  [Fix]
  
  Enable CONFIG_HUGETLBFS
  
  [Regression Potential]
  
  This config enables code that is disabled by default. However, there is
  minimal stub code running at boot so problems would most likely show up
  as splats during boot or later when hugetlbfs is explicitly turned on.

** Description changed:

  [Impact]
  
  Huge pages can't be managed via hugeadm which requires hugetlbfs.
  
  [Test Case]
  
  $ hugeadm --pool-list
  hugeadm:ERROR: kernel does not support huge pages
  
  With fix:
  $ hugeadm --pool-list
-       Size  Minimum  Current  Maximum  Default
-      65536        0        0        0         
-    2097152        0        0        0        *
-   33554432        0        0        0         
- 1073741824        0        0        0         
+       Size  Minimum  Current  Maximum  Default
+      65536        0        0        0
+    2097152        0        0        0        *
+   33554432        0        0        0
+ 1073741824        0        0        0
  
  [Fix]
  
  Enable CONFIG_HUGETLBFS
  
  [Regression Potential]
  
  This config enables code that is disabled by default. However, there is
  minimal stub code running at boot so problems would most likely show up
- as splats during boot or later when hugetlbfs is explicitly turned on.
+ as splats during boot or later on when hugetlbfs is explicitly mounted
+ by systemd.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933627

Title:
  HUGETLBFS is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1933627/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to