From db5ed33988a1d53066375c8f2ca34c28d81f0e17 Mon Sep 17 00:00:00 2001 From: Andrew Morton Date: Sun, 10 Mar 2013 21:54:49 +1100 Subject: [PATCH] memcg-debugging-facility-to-access-dangling-memcgs-fix fix up Kconfig text Cc: Glauber Costa Signed-off-by: Andrew Morton --- init/Kconfig | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/init/Kconfig b/init/Kconfig index cfad1e54c42a..b9327fb1a406 100644 --- a/init/Kconfig +++ b/init/Kconfig @@ -893,14 +893,14 @@ config MEMCG_KMEM will ever exhaust kernel resources alone. config MEMCG_DEBUG_ASYNC_DESTROY - bool "Memory Resource Controller Debug assynchronous object destruction" + bool "Memory Resource Controller Debug asynchronous object destruction" depends on MEMCG_KMEM || MEMCG_SWAP default n help - When a memcg is destroyed, the memory - consumed by it may not be immediately freed. This is because when some - extensions are used, such as swap or kernel memory, objects can - outlive the group and hold a reference to it. + When a memcg is destroyed, the memory consumed by it may not be + immediately freed. This is because when some extensions are used, such + as swap or kernel memory, objects can outlive the group and hold a + reference to it. If this is the case, the dangling_memcgs file will show information about what are the memcgs still alive, and which references are still -- 2.39.5