Section (2) alloc_hugepages
alloc_hugepages, free_hugepages — allocate or free huge pages
The system calls
free_hugepages() were introduced in Linux
2.5.36 and removed again in 2.5.54. They existed only on i386
and ia64 (when built with
CONFIG_HUGETLB_PAGE). In Linux 2.4.20, the
syscall numbers exist, but the calls fail with the error
On i386 the memory management hardware knows about ordinary pages (4 KiB) and huge pages (2 or 4 MiB). Similarly ia64 knows about huge pages of several sizes. These system calls serve to map huge pages into the process_zsingle_quotesz_s memory or to free them again. Huge pages are locked into memory, and are not swapped.
is an identifier. When zero the pages are private, and not
inherited by children. When positive the pages are shared
with other applications using the same
key, and inherited by child
free_hugepages() tells which
page is being freed: it was the return value of a call to
alloc_hugepages(). (The memory
is first actually freed when all users have released it.) The
addr argument of
alloc_hugepages() is a hint,
that the kernel may or may not follow. Addresses must be
is the length of the required segment. It must be a multiple
of the huge page size.
specifies the memory protection of the segment. It is one of
is ignored, unless
key is positive. In that case,
IPC_CREAT, then a new huge page
segment is created when none with the given key existed. If
this flag is not set, then ENOENT is returned when no segment with
the given key exists.
alloc_hugepages() returns the allocated
virtual address, and
free_hugepages() returns zero. On error,
−1 is returned, and
is set appropriately.
Number of configured hugetlb pages. This can be read and written.
Gives info on the number of configured hugetlb pages and on their size in the three variables HugePages_Total, HugePages_Free, Hugepagesize.
These calls are specific to Linux on Intel processors, and should not be used in programs intended to be portable.
These system calls are gone; they existed only in Linux 2.5.36 through to 2.5.54. Now the hugetlbfs filesystem can be used instead. Memory backed by huge pages (if the CPU supports them) is obtained by using mmap(2) to map files in this virtual filesystem.
The maximal number of huge pages can be specified using
This page is part of release 4.16 of the Linux
man-pages project. A
description of the project, information about reporting bugs,
and the latest version of this page, can be found at
Copyright 2003 Andries E. Brouwer (aebcwi.nl)
Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
preserved on all copies.
Permission is granted to copy and distribute modified versions of this
manual under the conditions for verbatim copying, provided that the
entire resulting derived work is distributed under the terms of a
permission notice identical to this one.
Since the Linux kernel and libraries are constantly changing, this
manual page may be incorrect or out-of-date. The author(s) assume no
responsibility for errors or omissions, or for damages resulting from
the use of the information contained herein. The author(s) may not
have taken the same level of care in the production of this manual,
which is licensed free of charge, as they might when working
Formatted or processed versions of this manual, if unaccompanied by
the source, must acknowledge the copyright and authors of this work.