Searched refs:mems (Results 1 – 16 of 16) sorted by relevance
/Linux-v5.15/drivers/remoteproc/ |
D | ti_k3_dsp_remoteproc.c | 58 const struct k3_dsp_mem_data *mems; member 432 data->mems[i].name); in k3_dsp_rproc_of_get_memories() 435 data->mems[i].name); in k3_dsp_rproc_of_get_memories() 442 data->mems[i].name); in k3_dsp_rproc_of_get_memories() 450 data->mems[i].name); in k3_dsp_rproc_of_get_memories() 454 kproc->mem[i].dev_addr = data->mems[i].dev_addr; in k3_dsp_rproc_of_get_memories() 458 data->mems[i].name, &kproc->mem[i].bus_addr, in k3_dsp_rproc_of_get_memories() 754 .mems = c66_mems, 761 .mems = c71_mems,
|
D | omap_remoteproc.c | 137 const struct omap_rproc_mem_data *mems; member 1065 .mems = ipu_mems, 1074 .mems = ipu_mems, 1079 .mems = dra7_dsp_mems, 1084 .mems = ipu_mems, 1184 if (!data->mems) in omap_rproc_of_get_internal_memories() 1195 for (i = 0; data->mems[i].name; i++) { in omap_rproc_of_get_internal_memories() 1197 data->mems[i].name); in omap_rproc_of_get_internal_memories() 1200 data->mems[i].name); in omap_rproc_of_get_internal_memories() 1206 data->mems[i].name); in omap_rproc_of_get_internal_memories() [all …]
|
/Linux-v5.15/drivers/gpu/drm/nouveau/nvif/ |
D | mmu.c | 40 static const struct nvif_mclass mems[] = { in nvif_mmu_ctor() local 64 ret = nvif_mclass(&mmu->object, mems); in nvif_mmu_ctor() 67 mmu->mem = mems[ret].oclass; in nvif_mmu_ctor()
|
/Linux-v5.15/tools/testing/selftests/vm/ |
D | hugetlb_reparenting_test.sh | 129 echo 0 >$CGROUP_ROOT/a/cpuset.mems 136 echo 0 >$CGROUP_ROOT/a/b/cpuset.mems 152 echo 0 >$CGROUP_ROOT/$cgroup/cpuset.mems
|
D | charge_reserved_hugetlb.sh | 105 echo 0 >$cgroup_path/$name/cpuset.mems
|
/Linux-v5.15/Documentation/x86/x86_64/ |
D | fake-numa-for-cpusets.rst | 51 [root@xroads /exampleset/ddset]# echo 0-1 > mems 57 available to them according to the fake nodes assigned as mems::
|
/Linux-v5.15/Documentation/admin-guide/cgroup-v1/ |
D | cpusets.rst | 175 - cpuset.mems: list of Memory Nodes in that cpuset 222 The cpus and mems files in the root (top_cpuset) cpuset are 224 cpu_online_mask using a CPU hotplug notifier, and the mems file 229 normally read-only copies of cpuset.cpus and cpuset.mems files 233 events will not change cpuset.cpus and cpuset.mems. Those events will 652 cpusets memory placement policy 'cpuset.mems' subsequently changes. 662 'cpuset.mems' file is modified, pages allocated to tasks in that 663 cpuset, that were on nodes in the previous setting of 'cpuset.mems', 664 will be moved to nodes in the new setting of 'mems.' 666 prior 'cpuset.mems' setting, will not be moved. [all …]
|
D | memcg_test.rst | 172 echo 0 > /opt/cpuset/01/cpuset.mems 176 echo 1 > /opt/cpuset/02/cpuset.mems
|
D | cgroups.rst | 336 /bin/echo 1 > cpuset.mems 360 if cpusets are enabled the user will have to populate the cpus and mems files
|
/Linux-v5.15/drivers/gpu/drm/nouveau/ |
D | nouveau_drm.c | 196 mems[] = { in nouveau_cli_init() local 280 ret = nvif_mclass(&cli->mmu.object, mems); in nouveau_cli_init() 286 cli->mem = &mems[ret]; in nouveau_cli_init()
|
/Linux-v5.15/Documentation/admin-guide/mm/ |
D | numa_memory_policy.rst | 274 mems 1-3 that sets an Interleave policy over the same set. If 275 the cpuset's mems change to 3-5, the Interleave will now occur 317 mems 2-5 that sets an Interleave policy over the same set with 318 MPOL_F_RELATIVE_NODES. If the cpuset's mems change to 3-7, the 319 interleave now occurs over nodes 3,5-7. If the cpuset's mems
|
/Linux-v5.15/Documentation/scheduler/ |
D | sched-capacity.rst | 309 echo 0 > /sys/fs/cgroup/cpuset/cs0/cpuset.mems 313 echo 0 > /sys/fs/cgroup/cpuset/cs1/cpuset.mems
|
D | sched-deadline.rst | 685 echo 0 > cpu0/cpuset.mems
|
/Linux-v5.15/Documentation/admin-guide/ |
D | cgroup-v2.rst | 2036 cpuset.mems 2048 # cat cpuset.mems 2053 "cpuset.mems" or all the available memory nodes if none 2056 The value of "cpuset.mems" stays constant until the next update 2059 Setting a non-empty value to "cpuset.mems" causes memory of 2065 So it is recommended that "cpuset.mems" should be set properly 2067 a need to change "cpuset.mems" with active tasks, it shouldn't 2070 cpuset.mems.effective 2078 If "cpuset.mems" is empty, it shows all the memory nodes from the 2080 Otherwise, it should be a subset of "cpuset.mems" unless none of [all …]
|
/Linux-v5.15/mm/ |
D | mempolicy.c | 2237 nodemask_t mems = cpuset_mems_allowed(current); in __mpol_dup() local 2238 mpol_rebind_policy(new, &mems); in __mpol_dup()
|
/Linux-v5.15/Documentation/filesystems/ |
D | proc.rst | 1659 being exhausted, the allowed memory represents the set of mems assigned to that
|