Lines Matching full:task
22 both cpusets and policies are applied to a task, the restrictions of the cpuset
46 Task/Process Policy
47 this is an optional, per-task policy. When defined for a
48 specific task, this policy controls all page allocations made
49 by or on behalf of the task that aren't controlled by a more
50 specific scope. If a task does not define a task policy, then
52 task policy "fall back" to the System Default Policy.
54 The task policy applies to the entire address space of a task. Thus,
56 [clone() w/o the CLONE_VM flag] and exec*(). This allows a parent task
57 to establish the task policy for a child task exec()'d from an
61 that a task may use to set/change its task/process policy.
63 In a multi-threaded task, task policies apply only to the thread
64 [Linux kernel task] that installs the policy and any threads
66 at the time a new task policy is installed retain their current
69 A task policy applies only to pages allocated after the policy is
70 installed. Any pages already faulted in by the task when the task
71 changes its task policy remain where they were allocated based on
77 A "VMA" or "Virtual Memory Area" refers to a range of a task's
78 virtual address space. A task may define a specific policy for a range
85 this region of the address space. Any regions of the task's
87 back to the task policy, which may itself fall back to the
93 pages allocated for anonymous segments, such as the task
106 region of a task's address space, and because the address
111 * A task may install a new VMA policy on a sub-range of a
131 range of a task's address space, shared policies apply
134 shared object, by any task, will obey the shared policy.
150 mappings that have not yet been written by the task, follow
151 task policy, if any, else System Default Policy.
155 the task that installs the policy for each range of distinct policy.
159 a shared memory region, when one task has installed shared policy on
185 For example, a NULL or default task policy will fall back to the
187 back to the task policy.
240 maintained per task. This counter wraps around to the lowest
259 the user should not be remapped if the task or VMA's set of allowed
269 nodes allowed by the task's cpuset, then the memory policy is
273 For example, consider a task that is attached to a cpuset with
288 by the user will be mapped relative to the set of the task or VMA's
308 relative to task or VMA's set of allowed nodes.
316 For example, consider a task that is attached to a cpuset with
329 set of memory nodes allowed by the task's cpuset, as that may
347 to '1', representing the reference held by the task that is installing the
349 structure, another reference is added, as the task's reference will be dropped
356 1) querying of the policy, either by the task itself [using the get_mempolicy()
357 API discussed below] or by another task using the /proc/<pid>/numa_maps
373 target task's task policy nor vma policies because we always acquire the
374 task's mm's mmap_lock for read during the query. The set_mempolicy() and
376 installing or replacing task or vma policies. Thus, there is no possibility
377 of a task or thread freeing a policy while another task or thread is
380 3) Page allocation usage of task or vma policy occurs in the fault path where
381 we hold them mmap_lock for read. Again, because replacing the task or vma
385 4) Shared policies require special consideration. One task can replace a
386 shared memory policy while another task, with a distinct mmap_lock, is
402 falling back to task or system default policy for shared memory regions,
412 always affect only the calling task, the calling task's address space, or
413 some shared object mapped into the calling task's address space.
422 Set [Task] Memory Policy::
427 Set's the calling task's "task/process memory policy" to mode
437 Get [Task] Memory Policy or Related Information::
443 Queries the "task/process memory policy" of the calling task, or the
450 Install VMA/Shared Policy for a Range of Task's Address Space::
457 VMA policy for the range of the calling task's address space specified
463 Set home node for a Range of Task's Address Spacec::
470 task's address range. The system call updates the home node only for the existing
483 + set the task policy for a specified program via set_mempolicy(2), fork(2) and
506 onto and folded into the task's set of allowed nodes as previously described.
514 cpuset information and requires that one know in what cpusets other task might