Lines Matching refs:memory
9 memory controller in this document. Do not confuse memory controller
10 used here with the memory controller that is used in hardware.
14 When we mention a cgroup (cgroupfs's directory) with memory controller,
15 we call it "memory cgroup". When you see git-log and source code, you'll
19 Benefits and Purpose of the memory controller
21 The memory controller isolates the memory behaviour of a group of tasks
23 uses of the memory controller. The memory controller can be used to
27 amount of memory.
28 b. Create a cgroup with a limited amount of memory; this can be used
30 c. Virtualization solutions can control the amount of memory they want
32 d. A CD/DVD burner could control the amount of memory used by the
34 of available memory.
43 - optionally, memory+swap usage can be accounted and limited.
48 - memory pressure notifier
52 Kernel memory support is a work in progress, and the current version provides
60 memory.usage_in_bytes # show current usage for memory
62 memory.memsw.usage_in_bytes # show current usage for memory+Swap
64 memory.limit_in_bytes # set/show limit of memory usage
65 memory.memsw.limit_in_bytes # set/show limit of memory+Swap usage
66 memory.failcnt # show the number of memory usage hits limits
67 memory.memsw.failcnt # show the number of memory+Swap hits limits
68 memory.max_usage_in_bytes # show max memory usage recorded
69 memory.memsw.max_usage_in_bytes # show max memory+Swap usage recorded
70 memory.soft_limit_in_bytes # set/show soft limit of memory usage
71 memory.stat # show various statistics
72 memory.use_hierarchy # set/show hierarchical account enabled
73 memory.force_empty # trigger forced move charge to parent
74 memory.pressure_level # set memory pressure notifications
75 memory.swappiness # set/show swappiness parameter of vmscan
77 memory.move_charge_at_immigrate # set/show controls of moving charges
78 memory.oom_control # set/show oom controls.
79 memory.numa_stat # show the number of memory usage per numa node
81 memory.kmem.limit_in_bytes # set/show hard limit for kernel memory
82 memory.kmem.usage_in_bytes # show current kernel memory allocation
83 memory.kmem.failcnt # show the number of kernel memory usage hits limits
84 memory.kmem.max_usage_in_bytes # show max kernel memory usage recorded
86 memory.kmem.tcp.limit_in_bytes # set/show hard limit for tcp buf memory
87 memory.kmem.tcp.usage_in_bytes # show current tcp buf memory allocation
88 memory.kmem.tcp.failcnt # show the number of tcp buf memory usage hits limits
89 memory.kmem.tcp.max_usage_in_bytes # show max tcp buf memory usage recorded
93 The memory controller has a long history. A request for comments for the memory
95 there were several implementations for memory control. The goal of the
97 for memory control. The first RSS controller was posted by Balbir Singh[2]
101 to allow user space handling of OOM. The current memory controller is
110 memory, the same physical memory needs to be reused to accomplish the task.
112 The memory controller implementation has been divided into phases. These
117 3. Kernel user memory accounting and slab control
120 The memory controller is the first controller developed.
125 page_counter tracks the current memory usage and limit of the group of
126 processes associated with the controller. Each cgroup has a memory controller
165 (*) page_cgroup structure is allocated at boot/memory-hotplug time.
199 the cgroup that brought it in -- this will happen on memory pressure).
206 be backed into memory in force, charges for pages are accounted against the
215 - memory.memsw.usage_in_bytes.
216 - memory.memsw.limit_in_bytes.
218 memsw means memory+swap. Usage of memory+swap is limited by
221 Example: Assume a system with 4G of swap. A task which allocates 6G of memory
222 (by mistake) under 2G memory limitation will use all swap.
227 * why 'memory+swap' rather than swap.
229 to move account from memory to swap...there is no change in usage of
230 memory+swap. In other words, when we want to limit the usage of swap without
231 affecting global LRU, memory+swap limit is better than just limiting swap from
234 * What happens when a cgroup hits memory.memsw.limit_in_bytes
235 When a cgroup hits memory.memsw.limit_in_bytes, it's useless to do swap-out
237 caches are dropped. But as mentioned above, global LRU can do swapout memory
238 from it for sanity of the system's memory management state. You can't forbid
245 to reclaim memory from the cgroup so as to make space for the new
278 With the Kernel memory extension, the Memory Controller is able to limit
279 the amount of kernel memory used by the system. Kernel memory is fundamentally
280 different than user memory, since it can't be swapped out, which makes it
283 Kernel memory won't be accounted at all until limit on a group is set. This
291 is removed. The memory limitation itself, can of course be removed by writing
292 -1 to memory.kmem.limit_in_bytes. In this case, kmem will be accounted, but not
295 Kernel memory limits are not imposed for the root cgroup. Usage for the root
296 cgroup may or may not be accounted. The memory used is accumulated into
297 memory.kmem.usage_in_bytes, or in a separate counter when it makes sense.
302 Currently no soft limit is implemented for kernel memory. It is future work
308 kernel memory, we prevent new processes from being created when the kernel
309 memory usage is too high.
318 * sockets memory pressure: some sockets protocols have memory pressure
322 * tcp memory pressure: sockets memory pressure for the tcp protocol.
326 Because the "kmem" counter is fed to the main user counter, kernel memory can
327 never be limited completely independently of user memory. Say "U" is the user
333 accounting. Kernel memory is completely ignored.
336 Kernel memory is a subset of the user memory. This setup is useful in
337 deployments where the total amount of memory per-cgroup is overcommited.
338 Overcommiting kernel memory limits is definitely not recommended, since the
339 box can still run out of non-reclaimable memory.
341 never greater than the total memory, and freely set U at the cost of his
343 WARNING: In the current implementation, memory reclaim will NOT be
349 triggered for the cgroup for both kinds of memory. This setup gives the
350 admin a unified view of memory, and it is also useful for people who just
351 want to track kernel memory usage.
364 # mkdir /sys/fs/cgroup/memory
365 # mount -t cgroup none /sys/fs/cgroup/memory -o memory
368 # mkdir /sys/fs/cgroup/memory/0
369 # echo $$ > /sys/fs/cgroup/memory/0/tasks
371 Since now we're in the 0 cgroup, we can alter the memory limit:
372 # echo 4M > /sys/fs/cgroup/memory/0/memory.limit_in_bytes
380 # cat /sys/fs/cgroup/memory/0/memory.limit_in_bytes
384 # cat /sys/fs/cgroup/memory/0/memory.usage_in_bytes
390 availability of memory on the system. The user is required to re-read
393 # echo 1 > memory.limit_in_bytes
394 # cat memory.limit_in_bytes
397 The memory.failcnt field gives the number of times that the cgroup limit was
400 The memory.stat file gives accounting information. Now, the number of
407 Performance test is also important. To see pure memory controller's overhead,
416 Trying usual test under memory controller is always helpful.
424 2. The user is using anonymous memory and swap is turned off or too low
462 memory.force_empty interface is provided to make cgroup's memory usage empty.
465 # echo 0 > memory.force_empty
473 Also, note that when memory.kmem.limit_in_bytes is set the charges due to
476 memory.kmem.usage_in_bytes == memory.usage_in_bytes.
482 memory.stat file includes following statistics
484 # per-memory cgroup local status
485 cache - # of bytes of page cache memory.
486 rss - # of bytes of anonymous and swap cache memory (includes
490 pgpgin - # of charging events to the memory cgroup. The charging
493 pgpgout - # of uncharging events to the memory cgroup. The uncharging
498 inactive_anon - # of bytes of anonymous and swap cache memory on inactive
500 active_anon - # of bytes of anonymous and swap cache memory on active
502 inactive_file - # of bytes of file-backed memory on inactive LRU list.
503 active_file - # of bytes of file-backed memory on active LRU list.
504 unevictable - # of bytes of memory that cannot be reclaimed (mlocked etc).
506 # status considering hierarchy (see memory.use_hierarchy settings)
508 hierarchical_memory_limit - # of bytes of memory limit with regard to hierarchy
509 under which the memory cgroup is
510 hierarchical_memsw_limit - # of bytes of memory+swap limit with regard to
511 hierarchy under which memory cgroup is.
531 Only anonymous and swap cache memory is listed as part of 'rss' stat.
533 amount of physical memory used by the cgroup.
536 file_mapped is accounted only when the memory cgroup is owner of page
551 A memory cgroup provides memory.failcnt and memory.memsw.failcnt files.
553 hit its limit. When a memory cgroup hits a limit, failcnt increases and
554 memory under it will be reclaimed.
557 # echo 0 > .../memory.failcnt
561 For efficiency, as other kernel components, memory cgroup uses some optimization
563 method and doesn't show 'exact' value of memory (and swap) usage, it's a fuzz
565 If you want to know more exact memory usage, you should use RSS+CACHE(+SWAP)
566 value in memory.stat(see 5.2).
580 The output format of memory.numa_stat is:
592 The memory controller supports a deep hierarchy and hierarchical accounting.
605 In the diagram above, with hierarchical accounting enabled, all memory
607 that has memory.use_hierarchy enabled. If one of the ancestors goes over its
613 A memory cgroup by default disables the hierarchy feature. Support
614 can be enabled by writing 1 to memory.use_hierarchy file of the root cgroup
616 # echo 1 > memory.use_hierarchy
620 # echo 0 > memory.use_hierarchy
631 Soft limits allow for greater sharing of memory. The idea behind soft limits
632 is to allow control groups to use as much of the memory as needed, provided
634 a. There is no memory contention
637 When the system detects memory contention or low memory, control groups
640 sure that one control group does not starve the others of memory.
643 no guarantees, but it does its best to make sure that when memory is
644 heavily contended for, memory is allocated based on the soft limit
653 # echo 256M > memory.soft_limit_in_bytes
657 # echo 1G > memory.soft_limit_in_bytes
660 reclaiming memory for balancing between memory cgroups
674 writing to memory.move_charge_at_immigrate of the destination cgroup.
678 # echo (some positive value) > memory.move_charge_at_immigrate
685 try to make space by reclaiming memory. Task migration may fail if we
691 # echo 0 > memory.move_charge_at_immigrate
698 (old) memory cgroup.
705 1 | A charge of file pages (normal file, tmpfs file (e.g. ipc shared memory)
721 Memory cgroup implements memory thresholds using the cgroups notification
722 API (see cgroups.txt). It allows to register multiple memory and memsw
727 - open memory.usage_in_bytes or memory.memsw.usage_in_bytes;
728 - write string like "<event_fd> <fd of memory.usage_in_bytes> <threshold>" to
731 Application will be notified through eventfd when memory usage crosses
738 memory.oom_control file is for OOM notification and other controls.
746 - open memory.oom_control file
747 - write string like "<event_fd> <fd of memory.oom_control>" to
753 You can disable the OOM-killer by writing "1" to memory.oom_control file, as:
755 #echo 1 > memory.oom_control
758 in memory cgroup's OOM-waitqueue when they request accountable memory.
760 For running them, you have to relax the memory cgroup's OOM status by
771 under_oom 0 or 1 (if 1, the memory cgroup is under OOM, tasks may
776 The pressure level notifications can be used to monitor the memory
778 different strategies of managing their memory resources. The pressure
781 The "low" level means that the system is reclaiming memory for new
787 The "medium" level means that the system is experiencing medium memory
790 vmstat/zoneinfo/memcg or internal memory usage statistics and free any
794 about to out of memory (OOM) or even the in-kernel OOM killer is on its
806 memory or thrashing. So, organize the cgroups wisely, or propagate the
810 The file memory.pressure_level is only used to setup an eventfd. To
814 - open memory.pressure_level;
815 - write string like "<event_fd> <fd of memory.pressure_level> <level>"
818 Application will be notified through eventfd when memory pressure is at
820 memory.pressure_level are no implemented.
825 memory limit, sets up a notification in the cgroup and then makes child
828 # cd /sys/fs/cgroup/memory/
831 # cgroup_event_listener memory.pressure_level low &
832 # echo 8000000 > memory.limit_in_bytes
833 # echo 8000000 > memory.memsw.limit_in_bytes
849 Overall, the memory controller has been a stable controller and has been
874 12. Corbet, Jonathan, Controlling memory use in cgroups,