admin-guide/cgroup-v1/memcg_test.rst

13 (*) Topics on API should be in Documentation/admin-guide/cgroup-v1/memory.rst)
22 	Allocated at boot or memory hotplug. Freed at memory hot removal.
203 	memory hotplug test is one of good test.
205 	to offline memory, do following::
207 		# echo offline > /sys/devices/system/memory/memoryXXX/state
209 	(XXX is the place of memory)
241 		# mount -t cgroup none /cgroup -o cpuset,memory,cpu,devices
256 		# mount -t cgroup none /cgroup -o memory
258 		# echo 40M > /cgroup/test/memory.limit_in_bytes
275 	Out-of-memory caused by memcg's limit will kill tasks under
287 		#echo 50M > /memory.limit_in_bytes
293 		#echo 50M > memory.limit_in_bytes
294 		#echo 50M > memory.memsw.limit_in_bytes
308 	run some programs which uses some amount of memory in /cgroup/A.
313 		#echo 1 >/cgroup/B/memory.move_charge_at_immigrate
317 	memory.stat of both A and B.
319 	See 8.2 of Documentation/admin-guide/cgroup-v1/memory.rst to see what value should
325 	Memory controller implements memory thresholds using cgroups notification
331 		# ./cgroup_event_listener /cgroup/A/memory.usage_in_bytes 5M
333 	(Shell-B) Add task to cgroup and try to allocate and free memory::
342 	Use /cgroup/A/memory.memsw.usage_in_bytes to test memsw thresholds.