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: linux-mm@kvack.org, xfs@oss.sgi.com
Subject: Re: memory reclaim problems on fs usage
Date: Sat, 14 Nov 2015 21:40:38 +0100	[thread overview]
Message-ID: <201511142140.38245.arekm@maven.pl> (raw)
In-Reply-To: <201511122228.26399.arekm@maven.pl>

On Thursday 12 of November 2015, Arkadiusz Miśkiewicz wrote:
> On Thursday 12 of November 2015, Tetsuo Handa wrote:
> > On 2015/11/12 15:06, Arkadiusz Miśkiewicz wrote:
> > > On Wednesday 11 of November 2015, Tetsuo Handa wrote:
> > >> Arkadiusz Mi?kiewicz wrote:
> > >>> This patch is against which tree? (tried 4.1, 4.2 and 4.3)
> > >> 
> > >> Oops. Whitespace-damaged. This patch is for vanilla 4.1.2.
> > >> Reposting with one condition corrected.
> > > 
> > > Here is log:
> > > 
> > > http://ixion.pld-linux.org/~arekm/log-mm-1.txt.gz
> > > 
> > > Uncompresses is 1.4MB, so not posting here.
> > 
> > Thank you for the log. The result is unexpected for me.
> 
> [...]
> 
> > vmstat_update() and submit_flushes() remained pending for about 110
> > seconds. If xlog_cil_push_work() were spinning inside GFP_NOFS
> > allocation, it should be reported as MemAlloc: traces, but no such lines
> > are recorded. I don't know why xlog_cil_push_work() did not call
> > schedule() for so long. Anyway, applying
> > http://lkml.kernel.org/r/20151111160336.GD1432@dhcp22.suse.cz should
> > solve vmstat_update() part.
> 
> To apply that patch on top of 4.1.13 I also had to apply patches listed
> below.
> 
> So in summary appllied:
> http://sprunge.us/GYBb
> http://sprunge.us/XWUX
> http://sprunge.us/jZjV

I've tried more to trigger "page allocation failure" with usual actions that 
triggered it previously but couldn't reproduce. With these patches applied it 
doesn't happen.

Logs from my tests:

http://ixion.pld-linux.org/~arekm/log-mm-3.txt.gz
http://ixion.pld-linux.org/~arekm/log-mm-4.txt.gz (with swap added)

But are these patches solving the problem or just hiding it?

-- 
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-14 20:40 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 [this message]
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
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=201511142140.38245.arekm@maven.pl \
    --to=arekm@maven.pl \
    --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: 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