From: Michal Hocko <mhocko@kernel.org>
To: Olaf Hering <olaf@aepfle.de>
Cc: 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>,
Greg KH <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>, Joonsoo Kim <js1304@gmail.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: OOM detection regressions since 4.7
Date: Mon, 29 Aug 2016 17:07:04 +0200 [thread overview]
Message-ID: <20160829150703.GH2968@dhcp22.suse.cz> (raw)
In-Reply-To: <20160829145203.GA30660@aepfle.de>
On Mon 29-08-16 16:52:03, Olaf Hering wrote:
> On Thu, Aug 25, Olaf Hering wrote:
>
> > On Thu, Aug 25, Michal Hocko wrote:
> >
> > > Any luck with the testing of this patch?
>
> I ran rc3 for a few hours on Friday amd FireFox was not killed.
> Now rc3 is running for a day with the usual workload and FireFox is
> still running.
Is the patch
(http://lkml.kernel.org/r/20160823074339.GB23577@dhcp22.suse.cz) applied?
> Today I noticed the nfsserver was disabled, probably since months already.
> Starting it gives a OOM, not sure if this is new with 4.7+.
> Full dmesg attached.
> [93348.306369] modprobe: page allocation failure: order:4, mode:0x26040c0(GFP_KERNEL|__GFP_COMP|__GFP_NOTRACK)
ok so order-4 (COSTLY allocation) has failed because
[...]
> [93348.313778] Node 0 DMA: 1*4kB (U) 0*8kB 0*16kB 1*32kB (U) 2*64kB (U) 1*128kB (U) 1*256kB (U) 0*512kB 1*1024kB (U) 1*2048kB (M) 3*4096kB (M) = 15908kB
> [93348.313803] Node 0 DMA32: 13633*4kB (UME) 8035*8kB (UME) 890*16kB (UME) 10*32kB (U) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 133372kB
> [93348.313822] Node 0 Normal: 14003*4kB (UME) 25*8kB (UME) 2*16kB (UM) 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 56244kB
the memory is too fragmented for such a large allocation. Failing
order-4 requests is not so severe because we do not invoke the oom
killer if they fail. Especially without GFP_REPEAT we do not even try
too hard. Recent oom detection changes shouldn't change this behavior.
--
Michal Hocko
SUSE Labs
--
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-29 15:07 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 [this message]
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
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=20160829150703.GH2968@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=Ralf-Peter.Rohbeck@quantum.com \
--cc=a.miskiewicz@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=js1304@gmail.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=markus@trippelsdorf.de \
--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).