From: Jan Kara <jack@suse.cz>
To: arekm@maven.pl
Cc: Michal Hocko <mhocko@kernel.org>,
linux-ext4@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm, oom: report compaction/migration stats for higher order requests
Date: Wed, 17 Aug 2016 12:57:11 +0200 [thread overview]
Message-ID: <20160817105711.GA6656@quack2.suse.cz> (raw)
In-Reply-To: <201608161318.25412.a.miskiewicz@gmail.com>
On Tue 16-08-16 13:18:25, Arkadiusz Miskiewicz wrote:
> On Monday 15 of August 2016, Michal Hocko wrote:
> > [Fixing up linux-mm]
> >
> > Ups I had a c&p error in the previous patch. Here is an updated patch.
>
>
> Going to apply this patch now and report again. I mean time what I have is a
>
> while (true); do echo "XX date"; date; echo "XX SLAB"; cat /proc/slabinfo ;
> echo "XX VMSTAT"; cat /proc/vmstat ; echo "XX free"; free; echo "XX DMESG";
> dmesg -T | tail -n 50; /bin/sleep 60;done 2>&1 | tee log
>
> loop gathering some data while few OOM conditions happened.
>
> I was doing "rm -rf copyX; cp -al original copyX" 10x in parallel.
>
> https://ixion.pld-linux.org/~arekm/p2/ext4/log-20160816.txt
Just one more debug idea to add on top of what Michal said: Can you enable
mm_shrink_slab_start and mm_shrink_slab_end tracepoints (via
/sys/kernel/debug/tracing/events/vmscan/mm_shrink_slab_{start,end}/enable)
and gather output from /sys/kernel/debug/tracing/trace_pipe while the copy
is running?
Because your slab caches seem to contain a lot of dentries as well (even
more than inodes in terms of numbers) so it may be that OOM is declared too
early before slab shrinkers can actually catch up...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
--
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>
prev parent reply other threads:[~2016-08-17 10:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 7:01 4.7.0, cp -al causes OOM Arkadiusz Miskiewicz
[not found] ` <20160812074340.GC3639@dhcp22.suse.cz>
2016-08-12 7:44 ` Michal Hocko
2016-08-13 1:42 ` Dave Chinner
2016-08-14 10:50 ` Michal Hocko
2016-08-23 2:20 ` Dave Chinner
[not found] ` <20160814125327.GF9248@dhcp22.suse.cz>
[not found] ` <20160815085129.GA3360@dhcp22.suse.cz>
2016-08-16 11:18 ` [PATCH] mm, oom: report compaction/migration stats for higher order requests Arkadiusz Miskiewicz
2016-08-16 14:10 ` Michal Hocko
2016-08-17 8:34 ` Arkadiusz Miśkiewicz
2016-08-17 9:29 ` Michal Hocko
2016-08-18 18:49 ` Arkadiusz Miskiewicz
2016-08-19 6:44 ` Vlastimil Babka
2016-08-21 21:19 ` Arkadiusz Miskiewicz
2016-08-22 7:02 ` Michal Hocko
2016-08-17 10:57 ` Jan Kara [this message]
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=20160817105711.GA6656@quack2.suse.cz \
--to=jack@suse.cz \
--cc=arekm@maven.pl \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
/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