From: Shakeel Butt <shakeelb@google.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Michal Hocko <mhocko@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Roman Gushchin <guro@fb.com>, Greg Thelen <gthelen@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux MM <linux-mm@kvack.org>, Cgroups <cgroups@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] memcg: oom: ignore oom warnings from memory.max
Date: Mon, 4 May 2020 07:57:05 -0700 [thread overview]
Message-ID: <CALvZod5T9pYG1xVHqNM=c68jgKPVXtKjuvV0DSAR+Ld_Mm1c4A@mail.gmail.com> (raw)
In-Reply-To: <939b6744-6556-2733-b83e-bf14e848dabd@I-love.SAKURA.ne.jp>
On Mon, May 4, 2020 at 7:20 AM Tetsuo Handa
<penguin-kernel@i-love.sakura.ne.jp> wrote:
>
> On 2020/05/04 22:54, Shakeel Butt wrote:
> > 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@I-love.SAKURA.ne.jp .
> Will that approach help you?
From what I understand, that patch is specifically for controlling
messages to consoles. The messages will still be in logs, right?
next prev parent reply other threads:[~2020-05-04 14:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 18:27 [PATCH] memcg: oom: ignore oom warnings from memory.max Shakeel Butt
2020-04-30 19:06 ` Roman Gushchin
2020-04-30 19:30 ` Johannes Weiner
2020-04-30 20:23 ` Roman Gushchin
2020-04-30 19:31 ` Shakeel Butt
2020-04-30 19:29 ` Johannes Weiner
2020-04-30 20:20 ` Shakeel Butt
2020-05-04 6:57 ` Michal Hocko
2020-05-04 13:54 ` Shakeel Butt
2020-05-01 1:39 ` Yafang Shao
2020-05-01 2:04 ` Shakeel Butt
2020-05-01 2:12 ` Yafang Shao
2020-05-04 7:03 ` Michal Hocko
2020-05-04 7:26 ` Yafang Shao
2020-05-04 7:35 ` Michal Hocko
2020-05-04 7:40 ` Yafang Shao
2020-05-04 8:03 ` Michal Hocko
2020-05-04 6:56 ` Michal Hocko
2020-05-04 13:54 ` Shakeel Butt
2020-05-04 14:11 ` Michal Hocko
2020-05-04 14:53 ` Shakeel Butt
2020-05-04 15:00 ` Michal Hocko
2020-05-04 15:35 ` Shakeel Butt
2020-05-04 15:39 ` Yafang Shao
2020-05-04 16:06 ` Michal Hocko
2020-05-04 19:23 ` Shakeel Butt
2020-05-05 7:13 ` Michal Hocko
2020-05-05 15:03 ` Shakeel Butt
2020-05-05 16:57 ` Johannes Weiner
2020-05-05 15:27 ` Johannes Weiner
2020-05-05 15:35 ` Shakeel Butt
2020-05-05 15:49 ` Michal Hocko
2020-05-05 16:40 ` Johannes Weiner
2020-05-04 14:20 ` Tetsuo Handa
2020-05-04 14:57 ` Shakeel Butt [this message]
2020-05-04 15:44 ` Tetsuo Handa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALvZod5T9pYG1xVHqNM=c68jgKPVXtKjuvV0DSAR+Ld_Mm1c4A@mail.gmail.com' \
--to=shakeelb@google.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=gthelen@google.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).