From: David Rientjes <rientjes@google.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
azurit@pobox.sk, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [merged] mm-memcg-handle-non-error-oom-situations-more-gracefully.patch removed from -mm tree
Date: Wed, 27 Nov 2013 19:20:37 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1311271914460.5120@chino.kir.corp.google.com> (raw)
In-Reply-To: <20131128031313.GK3556@cmpxchg.org>
On Wed, 27 Nov 2013, Johannes Weiner wrote:
> > It appears as though this work is being developed in Linus's tree rather
> > than -mm, so I'm asking if we should consider backing some of it out for
> > 3.14 instead.
>
> The changes fix a deadlock problem. Are they creating problems that
> are worse than deadlocks, that would justify their revert?
>
None that I am currently aware of, I'll continue to try them out. I'd
suggest just dropping the stable@kernel.org from the whole series though
unless there is another report of such a problem that people are running
into.
> Since we can't physically draw a perfect line, we should strive for a
> reasonable and intuitive line. After that it's rapidly diminishing
> returns. Killing something after that much reclaim effort without
> success is a completely reasonable and intuitive line to draw. It's
> also the line that has been drawn a long time ago and we're not
> breaking this because of a micro optmimization.
>
You don't think something like this is helpful after scanning a memcg will
a large number of processes?
We've had this patch internally since we started using memcg, it has
avoided some unnecessary oom killing.
---
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -1836,6 +1836,13 @@ static void mem_cgroup_out_of_memory(struct mem_cgroup *memcg, gfp_t gfp_mask,
if (!chosen)
return;
points = chosen_points * 1000 / totalpages;
+
+ /* One last chance to see if we really need to kill something */
+ if (mem_cgroup_margin(memcg) >= (1 << order)) {
+ put_task_struct(chosen);
+ return;
+ }
+
oom_kill_process(chosen, gfp_mask, order, points, totalpages, memcg,
NULL, "Memory cgroup out of memory");
}
--
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:[~2013-11-28 3:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <526028bd.k5qPj2+MDOK1o6ii%akpm@linux-foundation.org>
2013-11-27 23:08 ` David Rientjes
2013-11-27 23:33 ` Johannes Weiner
2013-11-28 0:56 ` David Rientjes
2013-11-28 2:18 ` Johannes Weiner
2013-11-28 2:38 ` David Rientjes
2013-11-28 3:13 ` Johannes Weiner
2013-11-28 3:20 ` David Rientjes [this message]
2013-11-28 3:52 ` Johannes Weiner
2013-11-30 0:00 ` David Rientjes
2013-11-30 0:51 ` Greg KH
2013-11-30 10:25 ` David Rientjes
2013-11-30 3:35 ` Johannes Weiner
2013-11-30 10:32 ` David Rientjes
2013-11-30 15:55 ` Johannes Weiner
2013-11-30 22:12 ` David Rientjes
2013-11-28 10:02 ` Michal Hocko
2013-11-30 0:05 ` David Rientjes
2013-12-02 13:12 ` Michal Hocko
2013-12-02 22:51 ` David Rientjes
2013-11-28 9:12 ` Michal Hocko
2013-11-30 3:37 ` Johannes Weiner
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=alpine.DEB.2.02.1311271914460.5120@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=azurit@pobox.sk \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
/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