Lines Matching refs:limit

45  - soft limit
50  - Root cgroup has no limit controls.
64  memory.limit_in_bytes		 # set/show limit of memory usage
65  memory.memsw.limit_in_bytes	 # set/show limit of memory+Swap usage
70  memory.soft_limit_in_bytes	 # set/show soft limit of memory usage
81  memory.kmem.limit_in_bytes      # set/show hard limit for kernel memory
86  memory.kmem.tcp.limit_in_bytes  # set/show hard limit for tcp buf memory
125 page_counter tracks the current memory usage and limit of the group of
161 charged is over its limit. If it is, then reclaim is invoked on the cgroup.
224 By using the memsw limit, you can avoid system OOM which can be caused by swap
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
244 global VM. When a cgroup goes over its limit, we first try
278 With the Kernel memory extension, the Memory Controller is able to limit
283 Kernel memory won't be accounted at all until limit on a group is set. This
284 allows for existing setups to continue working without disruption.  The limit
286 cgroup. Attempting to set the limit under those conditions will return -EBUSY.
288 automatically be accounted regardless of their limit value.
302 Currently no soft limit is implemented for kernel memory. It is future work
328 limit, and "K" the kernel limit. There are three possible ways limits can be
371 Since now we're in the 0 cgroup, we can alter the memory limit:
388 this limit to the value written into the file. This can be due to a
397 The memory.failcnt field gives the number of times that the cgroup limit was
423 1. The cgroup limit is too low (just too low to do anything useful)
508 hierarchical_memory_limit - # of bytes of memory limit with regard to hierarchy
510 hierarchical_memsw_limit - # of bytes of memory+swap limit with regard to
544 Please note that unlike during the global reclaim, limit reclaim
553 hit its limit. When a memory cgroup hits a limit, failcnt increases and
608 limit, the reclaim algorithm reclaims from the tasks in the ancestor and the
635 b. They do not exceed their hard limit
638 are pushed back to their soft limits. If the soft limit of each control
644 heavily contended for, memory is allocated based on the soft limit
645 hints/setup. Currently soft limit based reclaim is set up such that
651 assume a soft limit of 256 MiB)
661 NOTE2: It is recommended to set the soft limit always below the hard limit,
662        otherwise the hard limit will take precedence.
761 	* enlarge limit or reduce usage.
825    memory limit, sets up a notification in the cgroup and then makes child
844 3. Start reclamation in the background when the limit is