From: Lorenzo Stoakes <lstoakes@gmail.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Oleg Nesterov <oleg@redhat.com>,
Vladimir Davydov <vdavydov@parallels.com>,
Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Markus Trippelsdorf <markus@trippelsdorf.de>,
Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>,
Ralf-Peter Rohbeck <Ralf-Peter.Rohbeck@quantum.com>,
Jiri Slaby <jslaby@suse.com>, Olaf Hering <olaf@aepfle.de>,
Joonsoo Kim <js1304@gmail.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: More OOM problems
Date: Sun, 25 Sep 2016 22:48:23 +0100 [thread overview]
Message-ID: <20160925214823.GA9321@lucifer> (raw)
In-Reply-To: <20160919085348.GG10785@dhcp22.suse.cz>
On Mon, Sep 19, 2016 at 10:53:48AM +0200, Michal Hocko wrote:
> On Mon 19-09-16 09:42:37, Lorenzo Stoakes wrote:
> > On Mon, Sep 19, 2016 at 10:32:15AM +0200, Michal Hocko wrote:
> > >
> > > so this is the same thing as in Linus case. All the zones are hitting
> > > min wmark so the should_compact_retry() gave up. As mentioned in other
> > > email [1] this is inherent limitation of the workaround. Your system is
> > > swapless but there is a lot of the reclaimable page cache so Vlastimil's
> > > patches should help.
> >
> > I will experiment with a linux-next kernel and see if the problem
> > recurs. I've attempted to see if there is a way to manually reproduce
> > on the mainline kernel by performing workloads that triggered the
> > OOM (loading google sheets tabs, compiling a kernel, playing a video
> > on youtube), but to no avail - it seems the system needs to be
> > sufficiently fragmented first before it'll trigger.
> >
> > Given that's the case, I'll just have to try using the linux-next
> > kernel and if you don't hear from me you can assume it did not repro
> > again :)
>
> OK, fair deal ;)
Actually, I'll break the deal :) I've been running workloads similar to previous
weeks when I encountered the issue - including kernel builds, video playing,
lotsa tabs, etc. and also tried to intentionally eat up a bit of RAM from
time-to-time and have not seen a single OOM, so it looks like this is sorted it
for my system, notwithstanding Murphy's law.
(I ended up using the mm tree as irritatingly I couldn't get linux-next working
with the arch linux build system, but it definitely includes Vlastimil's
patches.)
--
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-09-25 21:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-18 20:03 More OOM problems Linus Torvalds
2016-09-18 20:26 ` Lorenzo Stoakes
2016-09-18 20:58 ` Linus Torvalds
2016-09-18 21:13 ` Vlastimil Babka
2016-09-18 21:34 ` Lorenzo Stoakes
2016-09-19 8:32 ` Michal Hocko
2016-09-19 8:42 ` Lorenzo Stoakes
2016-09-19 8:53 ` Michal Hocko
2016-09-25 21:48 ` Lorenzo Stoakes [this message]
2016-09-26 7:48 ` Michal Hocko
2016-09-18 21:00 ` Vlastimil Babka
2016-09-18 21:18 ` Linus Torvalds
2016-09-19 6:27 ` Jiri Slaby
2016-09-19 7:01 ` Michal Hocko
2016-09-19 7:52 ` Michal Hocko
2016-09-19 1:07 ` Andi Kleen
[not found] ` <alpine.DEB.2.20.1609190836540.12121@east.gentwo.org>
2016-09-19 14:31 ` Andi Kleen
2016-09-19 14:39 ` Michal Hocko
2016-09-19 14:41 ` Vlastimil Babka
2016-09-19 18:18 ` Linus Torvalds
2016-09-19 19:57 ` Christoph Lameter
2016-09-18 22:00 ` Vlastimil Babka
2016-09-19 6:56 ` Michal Hocko
2016-09-19 6:48 ` Michal Hocko
2016-09-21 7:04 ` Raymond Jennings
2016-09-21 7:29 ` Michal Hocko
2016-09-29 6:12 ` More OOM problems (sorry fro the mail bomb) Raymond Jennings
2016-09-29 7:03 ` Vlastimil Babka
2016-09-29 20:08 ` Raymond Jennings
2016-09-29 21:20 ` Vlastimil Babka
2016-09-30 19:48 ` Raymond Jennings
[not found] <eafb59b5-0a2b-0e28-ca79-f044470a2851@Quantum.com>
[not found] ` <20160930214448.GB28379@dhcp22.suse.cz>
[not found] ` <982671bd-5733-0cd5-c15d-112648ff14c5@Quantum.com>
2016-10-11 6:44 ` More OOM problems Michal Hocko
2016-10-11 7:10 ` Vlastimil Babka
2016-10-30 4:17 ` Simon Kirby
2016-10-31 21:41 ` Vlastimil Babka
2016-10-31 21:51 ` Vlastimil Babka
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=20160925214823.GA9321@lucifer \
--to=lstoakes@gmail.com \
--cc=Ralf-Peter.Rohbeck@quantum.com \
--cc=a.miskiewicz@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=js1304@gmail.com \
--cc=jslaby@suse.com \
--cc=linux-mm@kvack.org \
--cc=markus@trippelsdorf.de \
--cc=mhocko@suse.cz \
--cc=olaf@aepfle.de \
--cc=oleg@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=vdavydov@parallels.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;
as well as URLs for NNTP newsgroup(s).