Home
last modified time | relevance | path

Searched refs:mems (Results 1 – 12 of 12) sorted by relevance

/Linux-v5.4/drivers/gpu/drm/nouveau/nvif/
Dmmu.c39 static const struct nvif_mclass mems[] = { in nvif_mmu_init() local
63 ret = nvif_mclass(&mmu->object, mems); in nvif_mmu_init()
66 mmu->mem = mems[ret].oclass; in nvif_mmu_init()
/Linux-v5.4/Documentation/x86/x86_64/
Dfake-numa-for-cpusets.rst51 [root@xroads /exampleset/ddset]# echo 0-1 > mems
57 available to them according to the fake nodes assigned as mems::
/Linux-v5.4/Documentation/devicetree/bindings/iio/imu/
Dinv_mpu6050.txt3 http://www.invensense.com/mems/gyro/mpu6050.html
/Linux-v5.4/Documentation/admin-guide/cgroup-v1/
Dcpusets.rst173 - cpuset.mems: list of Memory Nodes in that cpuset
220 The cpus and mems files in the root (top_cpuset) cpuset are
222 cpu_online_mask using a CPU hotplug notifier, and the mems file
639 cpusets memory placement policy 'cpuset.mems' subsequently changes.
649 'cpuset.mems' file is modified, pages allocated to tasks in that
650 cpuset, that were on nodes in the previous setting of 'cpuset.mems',
651 will be moved to nodes in the new setting of 'mems.'
653 prior 'cpuset.mems' setting, will not be moved.
696 /bin/echo 1 > cpuset.mems
749 cpuset.cpu_exclusive cpuset.mems
[all …]
Dmemcg_test.rst181 echo 0 > /opt/cpuset/01/cpuset.mems
185 echo 1 > /opt/cpuset/02/cpuset.mems
Dcgroups.rst336 /bin/echo 1 > cpuset.mems
360 if cpusets are enabled the user will have to populate the cpus and mems files
/Linux-v5.4/drivers/gpu/drm/nouveau/
Dnouveau_drm.c193 mems[] = { in nouveau_cli_init() local
275 ret = nvif_mclass(&cli->mmu.object, mems); in nouveau_cli_init()
281 cli->mem = &mems[ret]; in nouveau_cli_init()
/Linux-v5.4/Documentation/admin-guide/mm/
Dnuma_memory_policy.rst267 mems 1-3 that sets an Interleave policy over the same set. If
268 the cpuset's mems change to 3-5, the Interleave will now occur
310 mems 2-5 that sets an Interleave policy over the same set with
311 MPOL_F_RELATIVE_NODES. If the cpuset's mems change to 3-7, the
312 interleave now occurs over nodes 3,5-7. If the cpuset's mems
/Linux-v5.4/Documentation/admin-guide/
Dcgroup-v2.rst1877 cpuset.mems
1889 # cat cpuset.mems
1894 "cpuset.mems" or all the available memory nodes if none
1897 The value of "cpuset.mems" stays constant until the next update
1900 cpuset.mems.effective
1908 If "cpuset.mems" is empty, it shows all the memory nodes from the
1910 Otherwise, it should be a subset of "cpuset.mems" unless none of
1911 the memory nodes listed in "cpuset.mems" can be granted. In this
1912 case, it will be treated just like an empty "cpuset.mems".
/Linux-v5.4/mm/
Dmempolicy.c2238 nodemask_t mems = cpuset_mems_allowed(current); in __mpol_dup() local
2239 mpol_rebind_policy(new, &mems); in __mpol_dup()
/Linux-v5.4/Documentation/scheduler/
Dsched-deadline.rst685 echo 0 > cpu0/cpuset.mems
/Linux-v5.4/Documentation/filesystems/
Dproc.txt1538 being exhausted, the allowed memory represents the set of mems assigned to that