Searched refs:MPOL_BIND (Results 1 – 7 of 7) sorted by relevance
| /Linux-v5.4/include/uapi/linux/ |
| D | mempolicy.h | 22 MPOL_BIND, enumerator
|
| /Linux-v5.4/mm/ |
| D | mempolicy.c | 400 [MPOL_BIND] = {
839 case MPOL_BIND: in get_policy_nodemask()
1799 if (unlikely(policy->mode == MPOL_BIND) && in policy_nodemask()
1819 WARN_ON_ONCE(policy->mode == MPOL_BIND && (gfp & __GFP_THISNODE)); in policy_node()
1863 case MPOL_BIND: { in mempolicy_slab_node()
1955 if ((*mpol)->mode == MPOL_BIND) in huge_node()
1996 case MPOL_BIND: in init_nodemask_of_mempolicy()
2043 case MPOL_BIND: in mempolicy_nodemask_intersects()
2259 case MPOL_BIND: in __mpol_equal()
2414 case MPOL_BIND: in mpol_misplaced()
[all …]
|
| /Linux-v5.4/tools/perf/util/ |
| D | mmap.c | 201 if (mbind(data, mmap_len, MPOL_BIND, &node_mask, 1, 0)) { in perf_mmap__aio_bind()
|
| /Linux-v5.4/Documentation/admin-guide/cgroup-v1/ |
| D | cpusets.rst | 613 mempolicy MPOL_BIND, and the nodes to which it was bound overlap with
615 of MPOL_BIND nodes are still allowed in the new cpuset. If the task
616 was using MPOL_BIND and now none of its MPOL_BIND nodes are allowed
618 was MPOL_BIND bound to the new cpuset (even though its NUMA placement,
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | tmpfs.txt | 116 allocation policy of MPOL_BIND | MPOL_F_STATIC_NODES.
|
| /Linux-v5.4/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.4/tools/perf/bench/ |
| D | numa.c | 351 ret = set_mempolicy(MPOL_BIND, &nodemask, sizeof(nodemask)*8); in bind_to_memnode()
|
