From: Michal Hocko <mhocko@kernel.org>
To: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
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 11:29:09 +0200 [thread overview]
Message-ID: <20160817092909.GA20703@dhcp22.suse.cz> (raw)
In-Reply-To: <201608171034.54940.arekm@maven.pl>
On Wed 17-08-16 10:34:54, Arkadiusz MiA?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
--
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-17 9:29 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 [this message]
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=20160817092909.GA20703@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=arekm@maven.pl \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.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