linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* [patch 10/17] mm/page_alloc.c: ratelimit allocation failure warnings more aggressively
@ 2019-11-06  5:16 akpm
  0 siblings, 0 replies; only message in thread
From: akpm @ 2019-11-06  5:16 UTC (permalink / raw)
  To: akpm, hannes, linux-mm, mm-commits, rientjes, torvalds

From: Johannes Weiner <hannes@cmpxchg.org>
Subject: mm/page_alloc.c: ratelimit allocation failure warnings more aggressively

While investigating a bug related to higher atomic allocation failures, we
noticed the failure warnings positively drowning the console, and in our
case trigger lockup warnings because of a serial console too slow to
handle all that output.

But even if we had a faster console, it's unclear what additional
information the current level of repetition provides.

Allocation failures happen for three reasons: The machine is OOM, the VM
is failing to handle reasonable requests, or somebody is making
unreasonable requests (and didn't acknowledge their opportunism with
__GFP_NOWARN).  Having the memory dump, a callstack, and the ratelimit
stats on skipped failure warnings should provide enough information to let
users/admins/developers know whether something is wrong and point them in
the right direction for debugging, bpftracing etc.

Limit allocation failure warnings to 1 spew every ten seconds.

Link: http://lkml.kernel.org/r/20191028194906.26899-1-hannes@cmpxchg.org
Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
Acked-by: David Rientjes <rientjes@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 mm/page_alloc.c |    7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

--- a/mm/page_alloc.c~mm-rate-limit-allocation-failure-warnings-more-aggressively
+++ a/mm/page_alloc.c
@@ -3728,10 +3728,6 @@ try_this_zone:
 static void warn_alloc_show_mem(gfp_t gfp_mask, nodemask_t *nodemask)
 {
 	unsigned int filter = SHOW_MEM_FILTER_NODES;
-	static DEFINE_RATELIMIT_STATE(show_mem_rs, HZ, 1);
-
-	if (!__ratelimit(&show_mem_rs))
-		return;
 
 	/*
 	 * This documents exceptions given to allocations in certain
@@ -3752,8 +3748,7 @@ void warn_alloc(gfp_t gfp_mask, nodemask
 {
 	struct va_format vaf;
 	va_list args;
-	static DEFINE_RATELIMIT_STATE(nopage_rs, DEFAULT_RATELIMIT_INTERVAL,
-				      DEFAULT_RATELIMIT_BURST);
+	static DEFINE_RATELIMIT_STATE(nopage_rs, 10*HZ, 1);
 
 	if ((gfp_mask & __GFP_NOWARN) || !__ratelimit(&nopage_rs))
 		return;
_


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2019-11-06  5:16 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-06  5:16 [patch 10/17] mm/page_alloc.c: ratelimit allocation failure warnings more aggressively akpm

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).