Lines Matching refs:kmem
88 memory.kmem.limit_in_bytes set/show hard limit for kernel memory
92 memory.kmem.usage_in_bytes show current kernel memory allocation
93 memory.kmem.failcnt show the number of kernel memory usage
95 memory.kmem.max_usage_in_bytes show max kernel memory usage recorded
97 memory.kmem.tcp.limit_in_bytes set/show hard limit for tcp buf memory
98 memory.kmem.tcp.usage_in_bytes show current tcp buf memory allocation
99 memory.kmem.tcp.failcnt show the number of tcp buf memory usage
101 memory.kmem.tcp.max_usage_in_bytes show max tcp buf memory usage recorded
322 memory.kmem.usage_in_bytes, or in a separate counter when it makes sense.
325 The main "kmem" counter is fed into the main counter, so kmem charges will
358 Because the "kmem" counter is fed to the main user counter, kernel memory can
364 This is the standard memcg limitation mechanism already present before kmem
382 Since kmem charges will also be fed to the user counter and reclaim will be
396 d. Enable CONFIG_MEMCG_KMEM (to use kmem extension)
530 Also, note that when memory.kmem.limit_in_bytes is set the charges due to
533 memory.kmem.usage_in_bytes == memory.usage_in_bytes.