From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: mhocko@kernel.org
Cc: elektron@halo.nu, linux-mm@kvack.org
Subject: Re: DOM Worker: page allocation stalls (4.9.13)
Date: Sat, 18 Mar 2017 10:30:46 +0900 [thread overview]
Message-ID: <201703181030.DII52105.FOQSVHFOFMOLJt@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20170317135440.GJ26298@dhcp22.suse.cz>
Michal Hocko wrote:
> > If you can rebuild your kernel, calling dump_tasks() in mm/oom_kill.c when
> > you hit warn_alloc() warnings might help.
>
> I do not really see how this would help much. If anything watching for
> /proc/vmstat counters would tell us much more.
Under memory pressure, read()/write() syscalls might involve significant delay
(including reading from /sys/kernel/debug/tracing/trace_pipe and writing to
a log file). Unless all problems are contained in a cgroup (which means that
administrators can diagnose from outside of that cgroup), it is silly to try to
read memory related information of a stalling system using userspace interface.
Therefore, automatic printk() is helpful than trying to start "cat /proc/vmstat"
from a shell. I wish there is a kernel function which does
"cat /proc/some_file" and/or "cat /sys/kernel/debug/tracing/trace_pipe" and
sends the output to printk() so that such actions will not involve significant
delay under memory pressure.
--
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>
prev parent reply other threads:[~2017-03-18 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 10:04 Philip J. Freeman
2017-03-17 8:46 ` Michal Hocko
2017-03-17 13:24 ` Tetsuo Handa
2017-03-17 13:54 ` Michal Hocko
2017-03-18 1:30 ` Tetsuo Handa [this message]
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=201703181030.DII52105.FOQSVHFOFMOLJt@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=elektron@halo.nu \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.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