Home
last modified time | relevance | path

Searched refs:MPOL_BIND (Results 1 – 6 of 6) sorted by relevance

/linux-4.1.27/include/uapi/linux/
Dmempolicy.h21 MPOL_BIND, enumerator
/linux-4.1.27/mm/
Dmempolicy.c465 [MPOL_BIND] = {
804 case MPOL_BIND: in get_policy_nodemask()
1641 if (unlikely(policy->mode == MPOL_BIND) && in policy_nodemask()
1658 case MPOL_BIND: in policy_zonelist()
1716 case MPOL_BIND: { in mempolicy_slab_node()
1823 if ((*mpol)->mode == MPOL_BIND) in huge_zonelist()
1864 case MPOL_BIND: in init_nodemask_of_mempolicy()
1911 case MPOL_BIND: in mempolicy_nodemask_intersects()
2131 case MPOL_BIND: in __mpol_equal()
2284 case MPOL_BIND: in mpol_misplaced()
[all …]
/linux-4.1.27/Documentation/cgroups/
Dcpusets.txt605 mempolicy MPOL_BIND, and the nodes to which it was bound overlap with
607 of MPOL_BIND nodes are still allowed in the new cpuset. If the task
608 was using MPOL_BIND and now none of its MPOL_BIND nodes are allowed
610 was MPOL_BIND bound to the new cpuset (even though its NUMA placement,
/linux-4.1.27/Documentation/filesystems/
Dtmpfs.txt115 allocation policy of MPOL_BIND | MPOL_F_STATIC_NODES.
/linux-4.1.27/Documentation/vm/
Dnuma_memory_policy.txt167 MPOL_BIND: This mode specifies that memory must come from the
319 path". Note that for MPOL_BIND, the "usage" extends across the entire
/linux-4.1.27/tools/perf/bench/
Dnuma.c294 ret = set_mempolicy(MPOL_BIND, &nodemask, sizeof(nodemask)*8); in bind_to_memnode()