Lines Matching full:task
20 both cpusets and policies are applied to a task, the restrictions of the cpuset
44 Task/Process Policy
45 this is an optional, per-task policy. When defined for a
46 specific task, this policy controls all page allocations made
47 by or on behalf of the task that aren't controlled by a more
48 specific scope. If a task does not define a task policy, then
50 task policy "fall back" to the System Default Policy.
52 The task policy applies to the entire address space of a task. Thus,
54 [clone() w/o the CLONE_VM flag] and exec*(). This allows a parent task
55 to establish the task policy for a child task exec()'d from an
59 that a task may use to set/change its task/process policy.
61 In a multi-threaded task, task policies apply only to the thread
62 [Linux kernel task] that installs the policy and any threads
64 at the time a new task policy is installed retain their current
67 A task policy applies only to pages allocated after the policy is
68 installed. Any pages already faulted in by the task when the task
69 changes its task policy remain where they were allocated based on
75 A "VMA" or "Virtual Memory Area" refers to a range of a task's
76 virtual address space. A task may define a specific policy for a range
83 this region of the address space. Any regions of the task's
85 back to the task policy, which may itself fall back to the
91 pages allocated for anonymous segments, such as the task
104 region of a task's address space, and because the address
109 * A task may install a new VMA policy on a sub-range of a
129 range of a task's address space, shared policies apply
132 shared object, by any task, will obey the shared policy.
148 mappings that have not yet been written by the task, follow
149 task policy, if any, else System Default Policy.
153 the task that installs the policy for each range of distinct policy.
157 a shared memory region, when one task has installed shared policy on
183 For example, a NULL or default task policy will fall back to the
185 back to the task policy.
238 maintained per task. This counter wraps around to the lowest
266 the user should not be remapped if the task or VMA's set of allowed
276 nodes allowed by the task's cpuset, then the memory policy is
280 For example, consider a task that is attached to a cpuset with
295 by the user will be mapped relative to the set of the task or VMA's
315 relative to task or VMA's set of allowed nodes.
323 For example, consider a task that is attached to a cpuset with
336 set of memory nodes allowed by the task's cpuset, as that may
354 to '1', representing the reference held by the task that is installing the
356 structure, another reference is added, as the task's reference will be dropped
363 1) querying of the policy, either by the task itself [using the get_mempolicy()
364 API discussed below] or by another task using the /proc/<pid>/numa_maps
380 target task's task policy nor vma policies because we always acquire the
381 task's mm's mmap_lock for read during the query. The set_mempolicy() and
383 installing or replacing task or vma policies. Thus, there is no possibility
384 of a task or thread freeing a policy while another task or thread is
387 3) Page allocation usage of task or vma policy occurs in the fault path where
388 we hold them mmap_lock for read. Again, because replacing the task or vma
392 4) Shared policies require special consideration. One task can replace a
393 shared memory policy while another task, with a distinct mmap_lock, is
409 falling back to task or system default policy for shared memory regions,
419 always affect only the calling task, the calling task's address space, or
420 some shared object mapped into the calling task's address space.
429 Set [Task] Memory Policy::
434 Set's the calling task's "task/process memory policy" to mode
444 Get [Task] Memory Policy or Related Information::
450 Queries the "task/process memory policy" of the calling task, or the
457 Install VMA/Shared Policy for a Range of Task's Address Space::
464 VMA policy for the range of the calling task's address space specified
470 Set home node for a Range of Task's Address Spacec::
477 task's address range. The system call updates the home node only for the existing
490 + set the task policy for a specified program via set_mempolicy(2), fork(2) and
513 onto and folded into the task's set of allowed nodes as previously described.
521 cpuset information and requires that one know in what cpusets other task might