From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Michal Hocko <mhocko@kernel.org>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
greg@suse.cz, Linus Torvalds <torvalds@linux-foundation.org>,
Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>,
Ralf-Peter Rohbeck <Ralf-Peter.Rohbeck@quantum.com>,
Jiri Slaby <jslaby@suse.com>, Olaf Hering <olaf@aepfle.de>,
Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: OOM detection regressions since 4.7
Date: Tue, 23 Aug 2016 09:40:14 +0200 [thread overview]
Message-ID: <20160823074014.GB15849@x4> (raw)
In-Reply-To: <20160823073318.GA23577@dhcp22.suse.cz>
On 2016.08.23 at 09:33 +0200, Michal Hocko wrote:
> On Tue 23-08-16 13:52:45, Joonsoo Kim wrote:
> [...]
> > Hello, Michal.
> >
> > I agree with partial revert but revert should be a different form.
> > Below change try to reuse should_compact_retry() version for
> > !CONFIG_COMPACTION but it turned out that it also causes regression in
> > Markus report [1].
>
> I would argue that CONFIG_COMPACTION=n behaves so arbitrary for high
> order workloads that calling any change in that behavior a regression
> is little bit exaggerated. Disabling compaction should have a very
> strong reason. I haven't heard any so far. I am even wondering whether
> there is a legitimate reason for that these days.
BTW, the current config description:
CONFIG_COMPACTION:
Allows the compaction of memory for the allocation of huge pages.
doesn't make it clear to the user that this is an essential feature.
--
Markus
--
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-08-23 7:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 9:32 OOM detection regressions since 4.7 Michal Hocko
2016-08-22 9:37 ` Michal Hocko
2016-08-22 10:05 ` Greg KH
2016-08-22 10:54 ` Michal Hocko
2016-08-22 13:31 ` Greg KH
2016-08-22 13:42 ` Michal Hocko
2016-08-22 14:02 ` Greg KH
2016-08-22 22:05 ` Andrew Morton
2016-08-23 7:43 ` Michal Hocko
2016-08-25 7:11 ` Michal Hocko
2016-08-25 7:17 ` Olaf Hering
2016-08-29 14:52 ` Olaf Hering
2016-08-29 14:54 ` Olaf Hering
2016-08-29 15:07 ` Michal Hocko
2016-08-29 15:59 ` Olaf Hering
2016-08-29 17:28 ` Linus Torvalds
2016-08-29 17:52 ` Jeff Layton
2016-08-28 5:50 ` Arkadiusz Miskiewicz
2016-08-25 20:30 ` Ralf-Peter Rohbeck
2016-08-26 6:26 ` Michal Hocko
2016-08-26 20:17 ` Ralf-Peter Rohbeck
2016-08-22 10:16 ` Markus Trippelsdorf
2016-08-22 10:56 ` Michal Hocko
2016-08-22 11:01 ` Markus Trippelsdorf
2016-08-22 11:13 ` Michal Hocko
2016-08-22 11:20 ` Markus Trippelsdorf
2016-08-23 4:52 ` Joonsoo Kim
2016-08-23 7:33 ` Michal Hocko
2016-08-23 7:40 ` Markus Trippelsdorf [this message]
2016-08-23 7:48 ` Michal Hocko
2016-08-23 19:08 ` Linus Torvalds
2016-08-24 6:32 ` Michal Hocko
2016-08-24 5:01 ` Joonsoo Kim
2016-08-24 7:04 ` Michal Hocko
2016-08-24 7:29 ` Joonsoo Kim
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=20160823074014.GB15849@x4 \
--to=markus@trippelsdorf.de \
--cc=Ralf-Peter.Rohbeck@quantum.com \
--cc=a.miskiewicz@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@suse.cz \
--cc=iamjoonsoo.kim@lge.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=olaf@aepfle.de \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@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;
as well as URLs for NNTP newsgroup(s).