On Wed, Sep 6, 2017 at 2:58 AM, Jesper Louis Andersen <
jesper.louis.ander...@gmail.com> wrote:
> It is correct that you get superpages/hugepages automatically if they are
> enabled. But your software must also allocate pages in a way which lets the
> operating system carve out a huge page
It is correct that you get superpages/hugepages automatically if they are
enabled. But your software must also allocate pages in a way which lets the
operating system carve out a huge page through a mmap() call (or similar).
If the hugepage is 2 megabytes and your garbage collector allocates in
What is the issue you are facing?
You do not need to do anything special to enable Hugepages for Go.
Huge page size is a kernel property usually set at Kernel compilation time
or set by your Linux Distribution.
Go does not care about what the underlying page size is, the page size is
