1 .\" This manpage is Copyright (C) 2006 Silicon Graphics, Inc.
4 .\" %%%LICENSE_START(VERBATIM_TWO_PARA)
5 .\" Permission is granted to make and distribute verbatim copies of this
6 .\" manual provided the copyright notice and this permission notice are
7 .\" preserved on all copies.
9 .\" Permission is granted to copy and distribute modified versions of this
10 .\" manual under the conditions for verbatim copying, provided that the
11 .\" entire resulting derived work is distributed under the terms of a
12 .\" permission notice identical to this one.
15 .\" FIXME Should programs normally be using move_pages() directly, or should
16 .\" they rather be using interfaces in the numactl package?
17 .\" (e.g., compare with recommendation in mbind(2)).
18 .\" Does this page need to give advice on this topic?
20 .TH MOVE_PAGES 2 2021-03-22 "Linux" "Linux Programmer's Manual"
22 move_pages \- move individual pages of a process to another node
25 .B #include <numaif.h>
27 .BI "long move_pages(int " pid ", unsigned long " count ", void **" pages ,
28 .BI " const int *" nodes ", int *" status ", int " flags );
31 Link with \fI\-lnuma\fP.
34 There is no glibc wrapper for this system call; see NOTES.
41 to the memory nodes specified by
43 The result of the move is reflected in
47 indicate constraints on the pages to be moved.
50 is the ID of the process in which pages are to be moved.
55 moves pages of the calling process.
57 To move pages in another process requires the following privileges:
59 In kernels up to and including Linux 4.12:
60 the caller must be privileged
62 or the real or effective user ID of the calling process must match the
63 real or saved-set user ID of the target process.
65 The older rules allowed the caller to discover various
66 virtual address choices made by the kernel that could lead
67 to the defeat of address-space-layout randomization
68 for a process owned by the same UID as the caller,
69 the rules were changed starting with Linux 4.13.
71 .\" commit 197e7e521384a23b9e585178f3f11c9fa08274b9
72 permission is governed by a ptrace access mode
73 .B PTRACE_MODE_READ_REALCREDS
74 check with respect to the target process; see
78 is the number of pages to move.
79 It defines the size of the three arrays
86 is an array of pointers to the pages that should be moved.
87 These are pointers that should be aligned to page boundaries.
88 .\" FIXME Describe the result if pointers in the 'pages' array are
89 .\" not aligned to page boundaries
90 Addresses are specified as seen by the process specified by
94 is an array of integers that specify the desired location for each page.
95 Each element in the array is a node number.
97 can also be NULL, in which case
99 does not move any pages but instead will return the node
100 where each page currently resides, in the
103 Obtaining the status of each page may be necessary to determine
104 pages that need to be moved.
107 is an array of integers that return the status of each page.
108 The array contains valid values only if
110 did not return an error.
111 Preinitialization of the array to a value
112 which cannot represent a real numa node or valid error of status array
113 could help to identify pages that have been migrated.
116 specify what types of pages to move.
118 means that only pages that are in exclusive use by the process
121 means that pages shared between multiple processes can also be moved.
122 The process must be privileged
125 .BR MPOL_MF_MOVE_ALL .
126 .SS Page states in the status array
127 The following values can be returned in each element of the
132 Identifies the node on which the page resides.
135 The page is mapped by multiple processes and can be moved only if
140 The page is currently busy and cannot be moved.
142 This occurs if a page is undergoing I/O or another kernel subsystem
143 is holding a reference to the page.
146 This is a zero page or the memory area is not mapped by the process.
149 Unable to write back a page.
150 The page has to be written back
151 in order to move it since the page is dirty and the filesystem
152 does not provide a migration function that would allow the move
156 A dirty page cannot be moved.
157 The filesystem does not
158 provide a migration function and has no ability to write back pages.
161 The page is not present.
164 Unable to allocate memory on target node.
169 .\" FIXME . Is the following quite true: does the wrapper in numactl
170 .\" do the right thing?
171 On error, it returns \-1, and sets
173 to indicate the error.
174 If positive value is returned, it is the number of
179 The number of nonmigrated pages if they were the result of nonfatal
181 .\" commit a49bd4d7163707de377aee062f17befef6da891b
185 Too many pages to move.
187 .\" commit 3140a2273009c01c27d316f35ab76a37e105fdd8
188 the kernel no longer generates this error.
191 .\" FIXME Clarify "current cpuset" in the description of the EACCES error.
192 .\" Is that the cpuset of the caller or the target?
193 One of the target nodes is not allowed by the current cpuset.
196 Parameter array could not be accessed.
203 was specified or an attempt was made to migrate pages of a kernel thread.
206 One of the target nodes is not online.
211 without sufficient privileges
212 .RB ( CAP_SYS_NICE ).
213 Or, the caller attempted to move pages of a process belonging
214 to another user but did not have privilege to do so
215 .RB ( CAP_SYS_NICE ).
218 Process does not exist.
221 first appeared on Linux in version 2.6.18.
223 This system call is Linux-specific.
225 Glibc does not provide a wrapper for this system call.
226 For information on library support, see
230 .BR get_mempolicy (2)
232 .B MPOL_F_MEMS_ALLOWED
233 flag to obtain the set of nodes that are allowed by
234 .\" FIXME Clarify "current cpuset". Is that the cpuset of the caller
237 Note that this information is subject to change at any
238 time by manual or automatic reconfiguration of the cpuset.
240 Use of this function may result in pages whose location
241 (node) violates the memory policy established for the
242 specified addresses (See
244 and/or the specified process (See
245 .BR set_mempolicy (2)).
246 That is, memory policy does not constrain the destination
252 header is not included with glibc, but requires installing
254 or a similar package.
256 .BR get_mempolicy (2),
258 .BR set_mempolicy (2),
263 .BR migratepages (8),