Thread (36 messages) 36 messages, 6 authors, 2020-05-05

Re: [PATCH] memcg: oom: ignore oom warnings from memory.max

From: Tetsuo Handa <hidden>
Date: 2020-05-04 15:44:24
Also in: linux-mm, lkml

On 2020/05/04 23:57, Shakeel Butt wrote:
On Mon, May 4, 2020 at 7:20 AM Tetsuo Handa
[off-list ref] wrote:
quoted
On 2020/05/04 22:54, Shakeel Butt wrote:
quoted
It may not be a problem for an individual or small scale deployment
but when "sweep before tear down" is the part of the workflow for
thousands of machines cycling through hundreds of thousands of cgroups
then we can potentially flood the logs with not useful dumps and may
hide (or overflow) any useful information in the logs.
I'm proposing a patch which allows configuring which OOM-related messages
should be sent to consoles at
https://lkml.kernel.org/r/20200424024239.63607-1-penguin-kernel-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org .
Will that approach help you?
quoted
From what I understand, that patch is specifically for controlling
messages to consoles. The messages will still be in logs, right?
Right.

If you want to control which OOM-related messages should be sent to syslog,
we could use similar approach.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help