From: Michal Hocko <mhocko@suse.cz>
To: Ralf-Peter Rohbeck <Ralf-Peter.Rohbeck@quantum.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: OOM killer changes
Date: Tue, 16 Aug 2016 09:43:17 +0200 [thread overview]
Message-ID: <20160816074316.GD5001@dhcp22.suse.cz> (raw)
In-Reply-To: <20160816073246.GC5001@dhcp22.suse.cz>
On Tue 16-08-16 09:32:46, Michal Hocko wrote:
> On Mon 15-08-16 11:42:11, Ralf-Peter Rohbeck wrote:
> > This time the OOM killer hit much quicker. No btrfs balance, just compiling
> > the kernel with the new change did it.
> > Much smaller logs so I'm attaching them.
>
> Just to clarify. You have added the trace_printk for
> try_to_release_page, right? (after fixing it of course). If yes there is
> no single mention of that path failing which would support Joonsoo's
> theory... Could you try with his patch?
And then it would be great if you could test with the current linux-next
tree. Vlastimil has done some changes which might help. But even if they
don't then it would be better to add more changes on top of them.
--
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-16 7:43 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d8f3adcc-3607-1ef6-9ec5-82b2e125eef2@quantum.com>
2016-08-01 6:16 ` OOM killer changes Michal Hocko
[not found] ` <b1a39756-a0b5-1900-6575-d6e1f502cb26@Quantum.com>
[not found] ` <20160801182358.GB31957@dhcp22.suse.cz>
[not found] ` <30dbabc4-585c-55a5-9f3a-4e243c28356a@Quantum.com>
2016-08-01 19:26 ` Michal Hocko
2016-08-01 19:35 ` Ralf-Peter Rohbeck
2016-08-01 19:43 ` Michal Hocko
2016-08-01 19:52 ` Ralf-Peter Rohbeck
2016-08-01 20:09 ` Michal Hocko
2016-08-01 20:16 ` Ralf-Peter Rohbeck
2016-08-01 20:26 ` Michal Hocko
2016-08-01 21:14 ` Ralf-Peter Rohbeck
2016-08-01 21:27 ` Ralf-Peter Rohbeck
2016-08-02 7:10 ` Michal Hocko
2016-08-02 19:25 ` Ralf-Peter Rohbeck
2016-08-15 4:48 ` Ralf-Peter Rohbeck
2016-08-15 9:16 ` Vlastimil Babka
2016-08-15 15:01 ` Michal Hocko
2016-08-15 18:42 ` Ralf-Peter Rohbeck
2016-08-16 7:32 ` Michal Hocko
2016-08-16 7:43 ` Michal Hocko [this message]
2016-08-17 9:14 ` Ralf-Peter Rohbeck
2016-08-17 9:23 ` Vlastimil Babka
2016-08-17 9:28 ` Ralf-Peter Rohbeck
2016-08-17 9:33 ` Michal Hocko
2016-08-17 23:37 ` Ralf-Peter Rohbeck
2016-08-18 6:57 ` Vlastimil Babka
2016-08-18 20:01 ` Ralf-Peter Rohbeck
2016-08-18 20:12 ` Vlastimil Babka
2016-08-19 2:42 ` Ralf-Peter Rohbeck
2016-08-19 6:27 ` Vlastimil Babka
2016-08-19 7:33 ` Michal Hocko
2016-08-19 7:47 ` Vlastimil Babka
2016-08-19 8:26 ` Michal Hocko
2016-08-24 18:13 ` Ralf-Peter Rohbeck
2016-08-25 7:22 ` Michal Hocko
2016-08-25 20:35 ` Ralf-Peter Rohbeck
2016-08-26 8:35 ` Michal Hocko
2016-09-06 11:09 ` Vlastimil Babka
2016-08-23 5:02 ` Joonsoo Kim
2016-08-23 7:45 ` Michal Hocko
2016-08-17 0:26 ` Ralf-Peter Rohbeck
2016-08-17 7:43 ` Vlastimil Babka
2016-08-16 3:12 ` Joonsoo Kim
2016-08-16 7:44 ` Vlastimil Babka
2016-08-17 4:48 ` Ralf-Peter Rohbeck
2016-08-17 7:56 ` Vlastimil Babka
2016-08-17 8:16 ` Joonsoo Kim
2016-08-17 9:21 ` Ralf-Peter Rohbeck
2016-08-17 9:11 ` Ralf-Peter Rohbeck
2016-08-17 9:20 ` Vlastimil Babka
2016-08-02 7:11 ` Vlastimil Babka
2016-08-02 9:02 ` 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=20160816074316.GD5001@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=Ralf-Peter.Rohbeck@quantum.com \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.