Lines Matching refs:cgroup
141 mount -t cgroup -o cpuset none /opt/cpuset
182 echo 1 >/opt/cgroup/01/memory/use_hierarchy
183 mkdir /opt/cgroup/01/child_a
184 mkdir /opt/cgroup/01/child_b
191 /opt/cgroup/01/child_a/child_aa
192 /opt/cgroup/01/child_b/child_bb
193 /opt/cgroup/01/child_c
199 race and lock dependency with other cgroup subsystems.
202 # mount -t cgroup none /cgroup -o cpuset,memory,cpu,devices
213 # mount -t cgroup none /cgroup -o memory
214 # mkdir /cgroup/test
215 # echo 40M > /cgroup/test/memory.limit_in_bytes
216 # echo 0 > /cgroup/test/tasks
219 # move all tasks in /cgroup/test to /cgroup
221 # rmdir /cgroup/test
248 #mkdir /cgroup/A
249 #echo $$ >/cgroup/A/tasks
250 run some programs which uses some amount of memory in /cgroup/A.
253 #mkdir /cgroup/B
254 #echo 1 >/cgroup/B/memory.move_charge_at_immigrate
255 #echo "pid of the program running in group A" >/cgroup/B/tasks
264 API. You can use tools/cgroup/cgroup_event_listener.c to test it.
266 (Shell-A) Create cgroup and run event listener
267 # mkdir /cgroup/A
268 # ./cgroup_event_listener /cgroup/A/memory.usage_in_bytes 5M
270 (Shell-B) Add task to cgroup and try to allocate and free memory
271 # echo $$ >/cgroup/A/tasks
278 Use /cgroup/A/memory.memsw.usage_in_bytes to test memsw thresholds.
280 It's good idea to test root cgroup as well.