From: Marian Marinov <mm@1h.com>
To: Michal Hocko <mhocko@suse.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [RFC] oom, memcg: handle sysctl oom_kill_allocating_task while memcg oom happening
Date: Tue, 10 Jun 2014 14:35:02 +0300 [thread overview]
Message-ID: <5396ED66.7090401@1h.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
a while back in 2012 there was a request for this functionality.
oom, memcg: handle sysctl oom_kill_allocating_task while memcg oom happening
This is the thread: https://lkml.org/lkml/2012/10/16/168
Now we run a several machines with around 10k processes on each machine, using containers.
Regularly we see OOM from within a container that causes performance degradation.
We are running 3.12.20 with the following OOM configuration and memcg oom enabled:
vm.oom_dump_tasks = 0
vm.oom_kill_allocating_task = 1
vm.panic_on_oom = 0
When OOM occurs we see very high numbers for the loadavg and the overall responsiveness of the machine degrades.
During these OOM states the load of the machine gradualy increases from 25 up to 120 in the interval of 10minutes.
Once we manually bring down the memory usage of a container(killing some tasks) the load drops down to 25 within 5 to
7 minutes.
I read the whole thread from 2012 but I do not see the expected behavior that is described by the people that
commented the issue.
In this case, with real usage for this patch, would it be considered for inclusion?
Marian
- --
Marian Marinov
Founder & CEO of 1H Ltd.
Jabber/GTalk: hackman@jabber.org
ICQ: 7556201
Mobile: +359 886 660 270
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlOW7WYACgkQ4mt9JeIbjJTZCACgj74t6T9GkCS5RlQEF6NkTbed
xJwAoK93irH+FneDoNdSi2DBSnR7a76r
=zl6k
-----END PGP SIGNATURE-----
next reply other threads:[~2014-06-10 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 11:35 Marian Marinov [this message]
2014-06-10 11:52 ` [RFC] oom, memcg: handle sysctl oom_kill_allocating_task while memcg oom happening Michal Hocko
2014-06-10 14:42 ` Marian Marinov
2014-06-10 22:37 ` David Rientjes
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=5396ED66.7090401@1h.com \
--to=mm@1h.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
/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