summaryrefslogtreecommitdiffstats
path: root/man2/alloc_hugepages.2
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-15 19:41:07 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-15 19:41:07 +0000
commit3af6d22bb3850ab2bac67287e3a3d3b0e32868e5 (patch)
tree3ee7a3ec64525911fa865bb984c86d997d855527 /man2/alloc_hugepages.2
parentAdding debian version 6.05.01-1. (diff)
downloadmanpages-3af6d22bb3850ab2bac67287e3a3d3b0e32868e5.tar.xz
manpages-3af6d22bb3850ab2bac67287e3a3d3b0e32868e5.zip
Merging upstream version 6.7.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'man2/alloc_hugepages.2')
-rw-r--r--man2/alloc_hugepages.220
1 files changed, 10 insertions, 10 deletions
diff --git a/man2/alloc_hugepages.2 b/man2/alloc_hugepages.2
index 33671da..0aba97e 100644
--- a/man2/alloc_hugepages.2
+++ b/man2/alloc_hugepages.2
@@ -2,7 +2,7 @@
.\"
.\" SPDX-License-Identifier: Linux-man-pages-copyleft
.\"
-.TH alloc_hugepages 2 2023-03-30 "Linux man-pages 6.05.01"
+.TH alloc_hugepages 2 2023-10-31 "Linux man-pages 6.7"
.SH NAME
alloc_hugepages, free_hugepages \- allocate or free huge pages
.SH SYNOPSIS
@@ -15,7 +15,7 @@ size_t " len ,
.BI "int syscall(SYS_free_hugepages, void *" addr );
.\" asmlinkage int sys_free_hugepages(unsigned long addr);
.fi
-.PP
+.P
.IR Note :
glibc provides no wrappers for these system calls,
necessitating the use of
@@ -31,7 +31,7 @@ They existed only on i386 and ia64 (when built with
In Linux 2.4.20, the syscall numbers exist,
but the calls fail with the error
.BR ENOSYS .
-.PP
+.P
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
@@ -39,7 +39,7 @@ several sizes.
These system calls serve to map huge pages into the
process's memory or to free them again.
Huge pages are locked into memory, and are not swapped.
-.PP
+.P
The
.I key
argument is an identifier.
@@ -48,7 +48,7 @@ not inherited by children.
When positive the pages are shared with other applications using the same
.IR key ,
and inherited by child processes.
-.PP
+.P
The
.I addr
argument of
@@ -63,12 +63,12 @@ argument of
.BR alloc_hugepages ()
is a hint, that the kernel may or may not follow.
Addresses must be properly aligned.
-.PP
+.P
The
.I len
argument is the length of the required segment.
It must be a multiple of the huge page size.
-.PP
+.P
The
.I prot
argument specifies the memory protection of the segment.
@@ -76,7 +76,7 @@ It is one of
.BR PROT_READ ,
.BR PROT_WRITE ,
.BR PROT_EXEC .
-.PP
+.P
The
.I flag
argument is ignored, unless
@@ -124,11 +124,11 @@ Memory backed by huge pages (if the CPU supports them) is obtained by
using
.BR mmap (2)
to map files in this virtual filesystem.
-.PP
+.P
The maximal number of huge pages can be specified using the
.B hugepages=
boot parameter.
-.\".PP
+.\".P
.\" requires CONFIG_HUGETLB_PAGE (under "Processor type and features")
.\" and CONFIG_HUGETLBFS (under "Filesystems").
.\" mount \-t hugetlbfs hugetlbfs /huge