From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-ext4@vger.kernel.org, linux-mm@kvack.org, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] mm, oom: report compaction/migration stats for higher order requests
Date: Thu, 18 Aug 2016 20:49:42 +0200 [thread overview]
Message-ID: <201608182049.42261.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <20160817092909.GA20703@dhcp22.suse.cz>
On Wednesday 17 of August 2016, Michal Hocko wrote:
> On Wed 17-08-16 10:34:54, Arkadiusz Miśkiewicz wrote:
> [...]
>
> > 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
>
> Dohh, COMPACTION counters are events and those are different than other
> counters we have. They only have per-cpu representation and so we would
> have to do
> + for_each_online_cpu(cpu) {
> + struct vm_event_state *this = &per_cpu(vm_event_states,
> cpu); + ret += this->event[item];
> + }
>
> which is really nasty because, strictly speaking, we would have to do
> {get,put}_online_cpus around that loop and that uses locking and we do
> not want to possibly block in this path just because something is in the
> middle of the hotplug. So let's scratch that patch for now and sorry I
> haven't realized that earlier.
>
> > 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.
>
> OK
So with http://lkml.kernel.org/r/20160816031222.GC16913@js1304-P5Q-DELUXE
OOM no longer happens (all 10x rm/cp processes finished).
https://ixion.pld-linux.org/~arekm/p2/ext4/log-20160818.txt
On Wednesday 17 of August 2016, Jan Kara wrote:
> 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?
Here it is:
https://ixion.pld-linux.org/~arekm/p2/ext4/log-trace_pipe-20160818.txt.gz
--
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-18 18:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 7:01 4.7.0, cp -al causes OOM Arkadiusz Miskiewicz
2016-08-12 7:43 ` Michal Hocko
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
2016-08-14 12:51 ` Michal Hocko
2016-08-14 12:53 ` [PATCH] mm, oom: report compaction/migration stats for higher order requests Michal Hocko
2016-08-15 8:51 ` Michal Hocko
2016-08-16 11:18 ` 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-17 9:29 ` Michal Hocko
2016-08-18 18:49 ` Arkadiusz Miskiewicz [this message]
2016-08-19 6:44 ` Vlastimil Babka
2016-08-19 6:44 ` Vlastimil Babka
2016-08-21 21:19 ` Arkadiusz Miskiewicz
2016-08-22 7:02 ` Michal Hocko
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=201608182049.42261.a.miskiewicz@gmail.com \
--to=a.miskiewicz@gmail.com \
--cc=arekm@maven.pl \
--cc=jack@suse.cz \
--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 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.