From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Dmitry Monakhov <dmonakhov@openvz.org>, linux-mm@kvack.org
Cc: cgroups@vger.kernel.org, vdavydov.dev@gmail.com
Subject: Re: [PATCH 1/2] mm: add sysctl to control global OOM logging behaviour
Date: Wed, 8 Nov 2017 20:42:37 +0900 [thread overview]
Message-ID: <24fb6865-6cc5-2af0-3a99-ea9495791f66@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20171108091843.29349-1-dmonakhov@openvz.org>
On 2017/11/08 18:18, Dmitry Monakhov wrote:
> Our systems becomes bigger and bigger, but OOM still happens.
> This becomes serious problem for systems where OOM happens
> frequently(containers, VM) because each OOM generate pressure
> on dmesg log infrastructure. Let's allow system administrator
> ability to tune OOM dump behaviour
Majority of OOM killer related messages are from dump_header().
Thus, allow tuning __ratelimit(&oom_rs) might make sense.
But other lines
"%s: Kill process %d (%s) score %u or sacrifice child\n"
"Killed process %d (%s) total-vm:%lukB, anon-rss:%lukB, file-rss:%lukB, shmem-rss:%lukB\n"
"oom_reaper: reaped process %d (%s), now anon-rss:%lukB, file-rss:%lukB, shmem-rss:%lukB\n"
should not cause problems, for it is easy to exclude such lines from
your dmesg log infrastructure using fgrep match.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-11-08 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 9:18 Dmitry Monakhov
2017-11-08 9:18 ` [PATCH 2/2] mm: memcg control oom logging behavior Dmitry Monakhov
2017-11-08 11:42 ` Tetsuo Handa [this message]
2017-11-08 12:19 ` [PATCH 1/2] mm: add sysctl to control global OOM logging behaviour Dmitry Monakhov
2017-11-08 13:45 ` Tetsuo Handa
2017-11-09 12:56 ` Michal Hocko
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=24fb6865-6cc5-2af0-3a99-ea9495791f66@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=cgroups@vger.kernel.org \
--cc=dmonakhov@openvz.org \
--cc=linux-mm@kvack.org \
--cc=vdavydov.dev@gmail.com \
/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