From: Michal Hocko <mhocko@suse.cz> To: "Arkadiusz Miśkiewicz" <arekm@maven.pl> Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>, linux-mm@kvack.org, cl@linux.com, htejun@gmail.com, xfs@oss.sgi.com Subject: Re: memory reclaim problems on fs usage Date: Mon, 16 Nov 2015 17:15:18 +0100 [thread overview] Message-ID: <20151116161518.GI14116@dhcp22.suse.cz> (raw) In-Reply-To: <201511151549.35299.arekm@maven.pl> On Sun 15-11-15 15:49:35, Arkadiusz Miśkiewicz wrote: > On Sunday 15 of November 2015, Tetsuo Handa wrote: > > Arkadiusz Miskiewicz wrote: > > > On Sunday 15 of November 2015, Tetsuo Handa wrote: > > > > I think that the vmstat statistics now have correct values. > > > > > > > > > But are these patches solving the problem or just hiding it? > > > > > > > > Excuse me but I can't judge. > > > > > > > > If you are interested in monitoring how vmstat statistics are changing > > > > under stalled condition, you can try below patch. > > > > > > Here is log with this and all previous patches applied: > > > http://ixion.pld-linux.org/~arekm/log-mm-5.txt.gz > > > > Regarding "Node 0 Normal" (min:7104kB low:8880kB high:10656kB), > > all free: values look sane to me. I think that your problem was solved. > > Great, thanks! > > Will all (or part) of these patches > > http://sprunge.us/GYBb Migrate reserves are not a stable material I am afraid. "vmstat: explicitly schedule per-cpu work on the CPU we need it to run on" was not marked for stable either but I am not sure why it should make any difference for your load. I understand that testing this is really tedious but it would be better to know which of the patches actually made a difference. > http://sprunge.us/XWUX (after it gets merged) Yes I plan to mark this one for stable. > be pushed to stable@ or are too risky for stable ? > > > > > $ grep "Normal free:" log-mm-5.txt | cut -b 44- | awk -F' ' ' { print $4 } > > ' | cut -b 6- | sort -g 8608kB > > 8636kB > > 8920kB > > 8920kB > > 8952kB > > 8968kB > > 8980kB > > (...snipped...) > > 215364kB > > 290068kB > > 290428kB > > 291176kB > > 292836kB > > 303992kB > > 306468kB > > 318080kB > > 319548kB > > > > $ grep "Normal free:" log-mm-1.txt | cut -b 44- | awk -F' ' ' { print $4 } > > ' | cut -b 6- | sort -g 0kB > > 40kB > > 128kB > > 128kB > > 128kB > > 128kB > > 128kB > > 128kB > > 128kB > > 128kB > > (...snipped...) > > 412kB > > 616kB > > 1268kB > > 1544kB > > 1696kB > > 2756kB > > 2756kB > > 2756kB > > 2756kB > > 2756kB > > 2756kB > > 2756kB > > > -- > Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) -- Michal Hocko SUSE Labs _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@suse.cz> To: "Arkadiusz Miśkiewicz" <arekm@maven.pl> Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>, htejun@gmail.com, cl@linux.com, linux-mm@kvack.org, xfs@oss.sgi.com Subject: Re: memory reclaim problems on fs usage Date: Mon, 16 Nov 2015 17:15:18 +0100 [thread overview] Message-ID: <20151116161518.GI14116@dhcp22.suse.cz> (raw) In-Reply-To: <201511151549.35299.arekm@maven.pl> On Sun 15-11-15 15:49:35, Arkadiusz MiA?kiewicz wrote: > On Sunday 15 of November 2015, Tetsuo Handa wrote: > > Arkadiusz Miskiewicz wrote: > > > On Sunday 15 of November 2015, Tetsuo Handa wrote: > > > > I think that the vmstat statistics now have correct values. > > > > > > > > > But are these patches solving the problem or just hiding it? > > > > > > > > Excuse me but I can't judge. > > > > > > > > If you are interested in monitoring how vmstat statistics are changing > > > > under stalled condition, you can try below patch. > > > > > > Here is log with this and all previous patches applied: > > > http://ixion.pld-linux.org/~arekm/log-mm-5.txt.gz > > > > Regarding "Node 0 Normal" (min:7104kB low:8880kB high:10656kB), > > all free: values look sane to me. I think that your problem was solved. > > Great, thanks! > > Will all (or part) of these patches > > http://sprunge.us/GYBb Migrate reserves are not a stable material I am afraid. "vmstat: explicitly schedule per-cpu work on the CPU we need it to run on" was not marked for stable either but I am not sure why it should make any difference for your load. I understand that testing this is really tedious but it would be better to know which of the patches actually made a difference. > http://sprunge.us/XWUX (after it gets merged) Yes I plan to mark this one for stable. > be pushed to stable@ or are too risky for stable ? > > > > > $ grep "Normal free:" log-mm-5.txt | cut -b 44- | awk -F' ' ' { print $4 } > > ' | cut -b 6- | sort -g 8608kB > > 8636kB > > 8920kB > > 8920kB > > 8952kB > > 8968kB > > 8980kB > > (...snipped...) > > 215364kB > > 290068kB > > 290428kB > > 291176kB > > 292836kB > > 303992kB > > 306468kB > > 318080kB > > 319548kB > > > > $ grep "Normal free:" log-mm-1.txt | cut -b 44- | awk -F' ' ' { print $4 } > > ' | cut -b 6- | sort -g 0kB > > 40kB > > 128kB > > 128kB > > 128kB > > 128kB > > 128kB > > 128kB > > 128kB > > 128kB > > (...snipped...) > > 412kB > > 616kB > > 1268kB > > 1544kB > > 1696kB > > 2756kB > > 2756kB > > 2756kB > > 2756kB > > 2756kB > > 2756kB > > 2756kB > > > -- > Arkadiusz MiA?kiewicz, arekm / ( maven.pl | pld-linux.org ) -- 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:[~2015-11-16 16:15 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-11-10 22:13 memory reclaim problems on fs usage Arkadiusz Miśkiewicz 2015-11-10 22:13 ` Arkadiusz Miśkiewicz 2015-11-11 15:58 ` Tetsuo Handa 2015-11-11 15:58 ` Tetsuo Handa 2015-11-11 16:19 ` Arkadiusz Miśkiewicz 2015-11-11 16:19 ` Arkadiusz Miśkiewicz 2015-11-11 22:19 ` Tetsuo Handa 2015-11-11 22:19 ` Tetsuo Handa 2015-11-12 6:06 ` Arkadiusz Miśkiewicz 2015-11-12 6:06 ` Arkadiusz Miśkiewicz 2015-11-12 14:12 ` Tetsuo Handa 2015-11-12 14:12 ` Tetsuo Handa 2015-11-12 20:06 ` Dave Chinner 2015-11-12 20:06 ` Dave Chinner 2015-11-13 12:19 ` Tetsuo Handa 2015-11-13 12:19 ` Tetsuo Handa 2015-11-12 21:28 ` Arkadiusz Miśkiewicz 2015-11-12 21:28 ` Arkadiusz Miśkiewicz 2015-11-14 20:40 ` Arkadiusz Miśkiewicz 2015-11-14 20:40 ` Arkadiusz Miśkiewicz 2015-11-15 2:35 ` Tetsuo Handa 2015-11-15 2:35 ` Tetsuo Handa 2015-11-15 11:29 ` Arkadiusz Miśkiewicz 2015-11-15 11:29 ` Arkadiusz Miśkiewicz 2015-11-15 14:13 ` Tetsuo Handa 2015-11-15 14:13 ` Tetsuo Handa 2015-11-15 14:49 ` Arkadiusz Miśkiewicz 2015-11-15 14:49 ` Arkadiusz Miśkiewicz 2015-11-16 16:15 ` Michal Hocko [this message] 2015-11-16 16:15 ` Michal Hocko 2015-11-18 22:36 ` Arkadiusz Miśkiewicz 2015-11-18 22:36 ` Arkadiusz Miśkiewicz 2015-11-19 15:59 ` Tetsuo Handa 2015-11-19 15:59 ` Tetsuo Handa
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=20151116161518.GI14116@dhcp22.suse.cz \ --to=mhocko@suse.cz \ --cc=arekm@maven.pl \ --cc=cl@linux.com \ --cc=htejun@gmail.com \ --cc=linux-mm@kvack.org \ --cc=penguin-kernel@i-love.sakura.ne.jp \ --cc=xfs@oss.sgi.com \ /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: linkBe 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.