Lines Matching refs:kmem

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
292 -1 to memory.kmem.limit_in_bytes. In this case, kmem will be accounted, but not
297 memory.kmem.usage_in_bytes, or in a separate counter when it makes sense.
299 The main "kmem" counter is fed into the main counter, so kmem charges will
326 Because the "kmem" counter is fed to the main user counter, kernel memory can
332     This is the standard memcg limitation mechanism already present before kmem
348     Since kmem charges will also be fed to the user counter and reclaim will be
360 d. Enable CONFIG_MEMCG_KMEM (to use kmem extension)
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.