|
@@ -301,6 +301,13 @@ to trigger slab reclaim when those limits are reached.
|
|
|
kernel memory, we prevent new processes from being created when the kernel
|
|
|
memory usage is too high.
|
|
|
|
|
|
+* slab pages: pages allocated by the SLAB or SLUB allocator are tracked. A copy
|
|
|
+of each kmem_cache is created everytime the cache is touched by the first time
|
|
|
+from inside the memcg. The creation is done lazily, so some objects can still be
|
|
|
+skipped while the cache is being created. All objects in a slab page should
|
|
|
+belong to the same memcg. This only fails to hold when a task is migrated to a
|
|
|
+different memcg during the page allocation by the cache.
|
|
|
+
|
|
|
* sockets memory pressure: some sockets protocols have memory pressure
|
|
|
thresholds. The Memory Controller allows them to be controlled individually
|
|
|
per cgroup, instead of globally.
|