From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Vincent Li <vincent.mc.li@gmail.com>
Cc: Linux-MM <linux-mm@kvack.org>
Subject: Re: sysrq key f to trigger OOM manually
Date: Fri, 29 Mar 2019 07:45:53 +0900 [thread overview]
Message-ID: <fcf5dd0b-8e96-7512-b76a-65a74e5fd52f@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <CAK3+h2xjr_h-3D9952SPUpN1HadyLz13gFmsAZWSTx9uz0sO3Q@mail.gmail.com>
On 2019/03/29 6:37, Vincent Li wrote:
> Hi,
>
> not sure if this is the right place, I tried to use echo f >
> /proc/sysrq-trigger to manually trigger OOM, the OOM killer is
> triggered to kill a process, does it make sense to trigger OOM killer
> manually but not actually kill the process, this could be useful to
> diagnosis problem without actually killing a process in production
> box.
Why not use "/usr/bin/top -o %MEM" etc. ?
Reading from /proc will give you more information than from SysRq.
next prev parent reply other threads:[~2019-03-28 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 21:37 Vincent Li
2019-03-28 22:45 ` Tetsuo Handa [this message]
[not found] ` <CAK3+h2wB2x4p976cqA5UPXhz5bZ6mjK98xB8nGQ8hkBoW02k7g@mail.gmail.com>
[not found] ` <201903290006.x2T06fWZ001228@www262.sakura.ne.jp>
2019-03-29 1:04 ` Vincent Li
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=fcf5dd0b-8e96-7512-b76a-65a74e5fd52f@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=linux-mm@kvack.org \
--cc=vincent.mc.li@gmail.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