linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: htejun@gmail.com, cl@linux.com, mhocko@suse.com,
	linux-mm@kvack.org, xfs@oss.sgi.com
Subject: Re: memory reclaim problems on fs usage
Date: Sun, 15 Nov 2015 15:49:35 +0100	[thread overview]
Message-ID: <201511151549.35299.arekm@maven.pl> (raw)
In-Reply-To: <201511152313.IJI23764.OHVFJFMSFOtOLQ@I-love.SAKURA.ne.jp>

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
http://sprunge.us/XWUX (after it gets merged)

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 )

--
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>

  reply	other threads:[~2015-11-15 14:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10 22:13 Arkadiusz Miśkiewicz
2015-11-11 15:58 ` Tetsuo Handa
2015-11-11 16:19   ` Arkadiusz Miśkiewicz
2015-11-11 22:19     ` Tetsuo Handa
2015-11-12  6:06       ` Arkadiusz Miśkiewicz
2015-11-12 14:12         ` Tetsuo Handa
2015-11-12 20:06           ` Dave Chinner
2015-11-13 12:19             ` Tetsuo Handa
2015-11-12 21:28           ` Arkadiusz Miśkiewicz
2015-11-14 20:40             ` Arkadiusz Miśkiewicz
2015-11-15  2:35               ` Tetsuo Handa
2015-11-15 11:29                 ` Arkadiusz Miśkiewicz
2015-11-15 14:13                   ` Tetsuo Handa
2015-11-15 14:49                     ` Arkadiusz Miśkiewicz [this message]
2015-11-16 16:15                       ` Michal Hocko
2015-11-18 22:36                         ` Arkadiusz Miśkiewicz
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=201511151549.35299.arekm@maven.pl \
    --to=arekm@maven.pl \
    --cc=cl@linux.com \
    --cc=htejun@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --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: 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