Eric Lee / smarc-ti-linux-kernel

Download as
Browse Code ยป

Commit 92e793495597af4135d94314113bf13eafb0e663

Authored by Glauber Costa
Committed by Linus Torvalds
1 parent 107dab5c92

kmem: add slab-specific documentation about the kmem controller 

Signed-off-by: Glauber Costa <glommer@parallels.com>
Cc: Christoph Lameter <cl@linux.com>
Cc: David Rientjes <rientjes@google.com>
Cc: Frederic Weisbecker <fweisbec@redhat.com>
Cc: Greg Thelen <gthelen@google.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: JoonSoo Kim <js1304@gmail.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Mel Gorman <mel@csn.ul.ie>
Cc: Michal Hocko <mhocko@suse.cz>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Rik van Riel <riel@redhat.com>
Cc: Suleiman Souhlal <suleiman@google.com>
Cc: Tejun Heo <tj@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

Showing 1 changed file with 7 additions and 0 deletions Side-by-side Diff

Documentation/cgroups/memory.txt
Diff comments   View file @ 92e7934
... ... @@ -301,6 +301,13 @@
301 301 kernel memory, we prevent new processes from being created when the kernel
302 302 memory usage is too high.
303 303  
  304 +* slab pages: pages allocated by the SLAB or SLUB allocator are tracked. A copy
  305 +of each kmem_cache is created everytime the cache is touched by the first time
  306 +from inside the memcg. The creation is done lazily, so some objects can still be
  307 +skipped while the cache is being created. All objects in a slab page should
  308 +belong to the same memcg. This only fails to hold when a task is migrated to a
  309 +different memcg during the page allocation by the cache.
  310 +
304 311 * sockets memory pressure: some sockets protocols have memory pressure
305 312 thresholds. The Memory Controller allows them to be controlled individually
306 313 per cgroup, instead of globally.