[PATCH -next] mm/kmemleak: increase the max mem pool to 1M

[PATCH -next] mm/kmemleak: increase the max mem pool to 1M

[Qian Cai]

There are some machines with slow disk and fast CPUs. When they are
under memory pressure, it could take a long time to swap before the OOM
kicks in to free up some memory. As the results, it needs a large
mem pool for kmemleak or suffering from higher chance of a kmemleak
metadata allocation failure. 524288 proves to be the good number for all
architectures here. Increase the upper bound to 1M to leave some room
for the future.

Signed-off-by: Qian Cai <cai@lca.pw>
---
 lib/Kconfig.debug | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index e80a745a11e2..d962c72a8bb5 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -595,7 +595,7 @@ config DEBUG_KMEMLEAK
 config DEBUG_KMEMLEAK_MEM_POOL_SIZE
 	int "Kmemleak memory pool size"
 	depends on DEBUG_KMEMLEAK
-	range 200 40000
+	range 200 1000000
 	default 16000
 	help
 	  Kmemleak must track all the memory allocations to avoid
-- 
1.8.3.1

Re: [PATCH -next] mm/kmemleak: increase the max mem pool to 1M

[Catalin Marinas]

On Wed, Aug 14, 2019 at 02:32:52PM -0400, Qian Cai wrote:
> There are some machines with slow disk and fast CPUs. When they are
> under memory pressure, it could take a long time to swap before the OOM
> kicks in to free up some memory. As the results, it needs a large
> mem pool for kmemleak or suffering from higher chance of a kmemleak
> metadata allocation failure. 524288 proves to be the good number for all
> architectures here. Increase the upper bound to 1M to leave some room
> for the future.
> 
> Signed-off-by: Qian Cai <cai@lca.pw>

Acked-by: Catalin Marinas <catalin.marinas@arm.com>