Searched refs:MPOL_BIND (Results 1 – 7 of 7) sorted by relevance
/Linux-v5.10/include/uapi/linux/ |
D | mempolicy.h | 22 MPOL_BIND, enumerator
|
/Linux-v5.10/mm/ |
D | mempolicy.c | 426 [MPOL_BIND] = { 908 case MPOL_BIND: in get_policy_nodemask() 1876 if (unlikely(policy->mode == MPOL_BIND) && in policy_nodemask() 1895 WARN_ON_ONCE(policy->mode == MPOL_BIND && (gfp & __GFP_THISNODE)); in policy_node() 1939 case MPOL_BIND: { in mempolicy_slab_node() 2031 if ((*mpol)->mode == MPOL_BIND) in huge_node() 2072 case MPOL_BIND: in init_nodemask_of_mempolicy() 2118 case MPOL_BIND: in mempolicy_nodemask_intersects() 2338 case MPOL_BIND: in __mpol_equal() 2492 case MPOL_BIND: in mpol_misplaced() [all …]
|
/Linux-v5.10/tools/perf/util/ |
D | mmap.c | 115 if (mbind(data, mmap_len, MPOL_BIND, node_mask, node_index + 1 + 1, 0)) { in perf_mmap__aio_bind()
|
/Linux-v5.10/Documentation/admin-guide/cgroup-v1/ |
D | cpusets.rst | 626 mempolicy MPOL_BIND, and the nodes to which it was bound overlap with 628 of MPOL_BIND nodes are still allowed in the new cpuset. If the task 629 was using MPOL_BIND and now none of its MPOL_BIND nodes are allowed 631 was MPOL_BIND bound to the new cpuset (even though its NUMA placement,
|
/Linux-v5.10/Documentation/filesystems/ |
D | tmpfs.rst | 128 allocation policy of MPOL_BIND | MPOL_F_STATIC_NODES.
|
/Linux-v5.10/Documentation/admin-guide/mm/ |
D | numa_memory_policy.rst | 195 MPOL_BIND 355 path". Note that for MPOL_BIND, the "usage" extends across the entire
|
/Linux-v5.10/tools/perf/bench/ |
D | numa.c | 356 ret = set_mempolicy(MPOL_BIND, &nodemask, sizeof(nodemask)*8); in bind_to_memnode()
|