From: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
To: Michal Hocko <mhocko@kernel.org>
Cc: 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 10:34:54 +0200 [thread overview]
Message-ID: <201608171034.54940.arekm@maven.pl> (raw)
In-Reply-To: <20160816141007.GF17417@dhcp22.suse.cz>
On Tuesday 16 of August 2016, Michal Hocko wrote:
> 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
>
> David was right when assuming it would be the ext4 inode cache which
> consumes the large portion of the memory. /proc/slabinfo shows
> ext4_inode_cache consuming between 2.5 to 4.6G of memory.
>
> first value last-first
> pgmigrate_success 1861785 2157917
> pgmigrate_fail 335344 1400384
> compact_isolated 4106390 5777027
> compact_migrate_scanned 113962774 446290647
> compact_daemon_wake 17039 43981
> compact_fail 645 1039
> compact_free_scanned 381701557 793430119
> compact_success 217 307
> compact_stall 862 1346
>
> which means that we have invoked compaction 1346 times and failed in
> 77% of cases. It is interesting to see that the migration wasn't all
> that unsuccessful. We managed to migrate 1.5x more pages than failed. It
> smells like the compaction just backs off.
With "[PATCH] mm, oom: report compaction/migration stats for higher order
requests" patch:
https://ixion.pld-linux.org/~arekm/p2/ext4/log-20160817.txt
Didn't count much - all counters are 0
compaction_stall:0 compaction_fail:0 compact_migrate_scanned:0
compact_free_scanned:0 compact_isolated:0 pgmigrate_success:0 pgmigrate_fail:0
two processes were killed by OOM (rm and cp), the rest of rm/cp didn't finish
and I'm interrupting it to try that next patch:
> Could you try to test with
> patch from
> http://lkml.kernel.org/r/20160816031222.GC16913@js1304-P5Q-DELUXE please?
> Ideally on top of linux-next. You can add both the compaction counters
> patch in the oom report and high order atomic reserves patch on top.
Uhm, was going to use it on top of 4.7.[01] first.
> Thanks
--
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
--
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-17 8:34 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 [this message]
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
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=201608171034.54940.arekm@maven.pl \
--to=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