Lines Matching refs:task
16 both cpusets and policies are applied to a task, the restrictions of the cpuset
35 Task/Process Policy: this is an optional, per-task policy. When defined
36 for a specific task, this policy controls all page allocations made by or
37 on behalf of the task that aren't controlled by a more specific scope.
38 If a task does not define a task policy, then all page allocations that
39 would have been controlled by the task policy "fall back" to the System
42 The task policy applies to the entire address space of a task. Thus,
44 [clone() w/o the CLONE_VM flag] and exec*(). This allows a parent task
45 to establish the task policy for a child task exec()'d from an
48 that a task may use to set/change its task/process policy.
50 In a multi-threaded task, task policies apply only to the thread
51 [Linux kernel task] that installs the policy and any threads
53 at the time a new task policy is installed retain their current
56 A task policy applies only to pages allocated after the policy is
57 installed. Any pages already faulted in by the task when the task
58 changes its task policy remain where they were allocated based on
61 VMA Policy: A "VMA" or "Virtual Memory Area" refers to a range of a task's
62 virtual address space. A task may define a specific policy for a range
68 the address space. Any regions of the task's address space that don't
69 have an explicit VMA policy will fall back to the task policy, which may
75 allocated for anonymous segments, such as the task stack and heap, and
86 to a specific region of a task's address space, and because the address
91 A task may install a new VMA policy on a sub-range of a previously
107 to be an attribute of a range of a task's address space, shared policies
110 by any task, will obey the shared policy.
125 private mappings that have not yet been written by the task, follow
126 task policy, if any, else System Default Policy.
130 the task that installs the policy for each range of distinct policy.
134 a shared memory region, when one task has installed shared policy on
157 For example, a NULL or default task policy will fall back to the
159 back to the task policy.
207 per task. This counter wraps around to the lowest specified node
218 the user should not be remapped if the task or VMA's set of allowed
228 nodes allowed by the task's cpuset, then the memory policy is
232 For example, consider a task that is attached to a cpuset with
246 by the user will be mapped relative to the set of the task or VMA's
266 relative to task or VMA's set of allowed nodes.
274 For example, consider a task that is attached to a cpuset with
287 set of memory nodes allowed by the task's cpuset, as that may
304 to '1', representing the reference held by the task that is installing the
306 structure, another reference is added, as the task's reference will be dropped
313 1) querying of the policy, either by the task itself [using the get_mempolicy()
314 API discussed below] or by another task using the /proc/<pid>/numa_maps
330 target task's task policy nor vma policies because we always acquire the
331 task's mm's mmap_sem for read during the query. The set_mempolicy() and
333 installing or replacing task or vma policies. Thus, there is no possibility
334 of a task or thread freeing a policy while another task or thread is
337 3) Page allocation usage of task or vma policy occurs in the fault path where
338 we hold them mmap_sem for read. Again, because replacing the task or vma
342 4) Shared policies require special consideration. One task can replace a
343 shared memory policy while another task, with a distinct mmap_sem, is
359 falling back to task or system default policy for shared memory regions,
366 always affect only the calling task, the calling task's address space, or
367 some shared object mapped into the calling task's address space.
380 Set's the calling task's "task/process memory policy" to mode
396 Queries the "task/process memory policy" of the calling task, or
410 a VMA policy for the range of the calling task's address space
421 + set the task policy for a specified program via set_mempolicy(2), fork(2) and
442 onto and folded into the task's set of allowed nodes as previously described.
450 cpuset information and requires that one know in what cpusets other task might