All of lore.kernel.org
 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: Wed, 11 Nov 2015 17:19:42 +0100	[thread overview]
Message-ID: <201511111719.44035.arekm@maven.pl> (raw)
In-Reply-To: <5643658B.9090206@I-love.SAKURA.ne.jp>

On Wednesday 11 of November 2015, Tetsuo Handa wrote:
> On 2015/11/11 7:13, Arkadiusz Miśkiewicz wrote:
> > The usual (repeatable) problem is like this:
> > 
> > full dmesg: http://sprunge.us/VEiE (more in it then in partial log below)
> 
> Maybe somebody doing GFP_NOIO allocation which XFS driver doing GFP_NOFS
> allocation is waiting for is stalling inside memory allocator. I think that
> checking tasks which are stalling inside memory allocator would help.
> 
> Please try reproducing this problem with a debug printk() patch shown below
> applied. This is a patch which I used for debugging silent lockup problem.
> When memory allocation got stuck, lines with MemAlloc keyword will be
> printed.
> 
> ---
>   fs/xfs/kmem.c          |  10 ++-
>   fs/xfs/xfs_buf.c       |   3 +-
>   include/linux/mmzone.h |   1 +
>   include/linux/vmstat.h |   1 +
>   mm/page_alloc.c        | 217
> +++++++++++++++++++++++++++++++++++++++++++++++++ mm/vmscan.c            |
>  22 +++++
>   6 files changed, 249 insertions(+), 5 deletions(-)

This patch is against which tree? (tried 4.1, 4.2 and 4.3)

-- 
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
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: Wed, 11 Nov 2015 17:19:42 +0100	[thread overview]
Message-ID: <201511111719.44035.arekm@maven.pl> (raw)
In-Reply-To: <5643658B.9090206@I-love.SAKURA.ne.jp>

On Wednesday 11 of November 2015, Tetsuo Handa wrote:
> On 2015/11/11 7:13, Arkadiusz Miśkiewicz wrote:
> > The usual (repeatable) problem is like this:
> > 
> > full dmesg: http://sprunge.us/VEiE (more in it then in partial log below)
> 
> Maybe somebody doing GFP_NOIO allocation which XFS driver doing GFP_NOFS
> allocation is waiting for is stalling inside memory allocator. I think that
> checking tasks which are stalling inside memory allocator would help.
> 
> Please try reproducing this problem with a debug printk() patch shown below
> applied. This is a patch which I used for debugging silent lockup problem.
> When memory allocation got stuck, lines with MemAlloc keyword will be
> printed.
> 
> ---
>   fs/xfs/kmem.c          |  10 ++-
>   fs/xfs/xfs_buf.c       |   3 +-
>   include/linux/mmzone.h |   1 +
>   include/linux/vmstat.h |   1 +
>   mm/page_alloc.c        | 217
> +++++++++++++++++++++++++++++++++++++++++++++++++ mm/vmscan.c            |
>  22 +++++
>   6 files changed, 249 insertions(+), 5 deletions(-)

This patch is against which tree? (tried 4.1, 4.2 and 4.3)

-- 
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-11 16:19 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 [this message]
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
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=201511111719.44035.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 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.