From: Andrew Morton <akpm@linux-foundation.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: Oleg Nesterov <oleg@redhat.com>,
David Rientjes <rientjes@google.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH] oom: consider multi-threaded tasks in task_will_free_mem
Date: Tue, 17 May 2016 15:21:39 -0700 [thread overview]
Message-ID: <20160517152139.fbda59b7c66e8470575050e8@linux-foundation.org> (raw)
In-Reply-To: <20160517202856.GF12220@dhcp22.suse.cz>
On Tue, 17 May 2016 22:28:56 +0200 Michal Hocko <mhocko@kernel.org> wrote:
> Andrew, this is not in the mmotm tree now because I didn't feel really
> confortable with the patch without Oleg seeing it. But it seems Oleg is
> ok [1] with it so could you push it to Linus along with the rest of oom
> pile please?
Reluctant. The CONFIG_COMPACTION=n regression which Joonsoo identified
is quite severe. Before patch: 10000 forks succeed. After patch: 500
forks fail. Ouch.
How can we merge such a thing?
--
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:[~2016-05-17 22:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 9:19 Michal Hocko
2016-04-13 11:04 ` Tetsuo Handa
2016-04-13 13:08 ` Michal Hocko
2016-04-13 13:27 ` Tetsuo Handa
2016-04-13 13:45 ` Michal Hocko
2016-05-17 18:06 ` Oleg Nesterov
2016-04-26 13:57 ` Michal Hocko
2016-05-17 20:28 ` Michal Hocko
2016-05-17 22:21 ` Andrew Morton [this message]
2016-05-18 7:16 ` Michal Hocko
2016-05-17 18:42 ` Oleg Nesterov
2016-05-17 20:25 ` 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=20160517152139.fbda59b7c66e8470575050e8@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=oleg@redhat.com \
--cc=rientjes@google.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