I did some tests to be sure: /sys/kernel/mm/hugepages/hugepages-1048576kB/nr_hugepages : 0 /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages : 5 /sys/devices/system/node/node0/hugepages/hugepages-1048576kB/nr_hugepages : 0 /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages : 2 /sys/devices/system/node/node1/hugepages/hugepages-1048576kB/nr_hugepages : 0 /sys/devices/system/node/node1/hugepages/hugepages-2048kB/nr_hugepages : 3
That shows that /sys/kernel/mm/hugepages/* always holds the global aggregated view. This avoids some hazzle in !numa systems where /sys/devices/system/node doesn't even exists e.g. i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507921 Title: When hugepages is set vm.max_map_count is not automatically adjusted To manage notifications about this bug go to: https://bugs.launchpad.net/falkor/+bug/1507921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
