* sysrq key f to trigger OOM manually
@ 2019-03-28 21:37 Vincent Li
2019-03-28 22:45 ` Tetsuo Handa
0 siblings, 1 reply; 3+ messages in thread
From: Vincent Li @ 2019-03-28 21:37 UTC (permalink / raw)
To: Linux-MM
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.
Regards,
Vincent
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: sysrq key f to trigger OOM manually
2019-03-28 21:37 sysrq key f to trigger OOM manually Vincent Li
@ 2019-03-28 22:45 ` Tetsuo Handa
[not found] ` <CAK3+h2wB2x4p976cqA5UPXhz5bZ6mjK98xB8nGQ8hkBoW02k7g@mail.gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Tetsuo Handa @ 2019-03-28 22:45 UTC (permalink / raw)
To: Vincent Li; +Cc: Linux-MM
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: sysrq key f to trigger OOM manually
[not found] ` <201903290006.x2T06fWZ001228@www262.sakura.ne.jp>
@ 2019-03-29 1:04 ` Vincent Li
0 siblings, 0 replies; 3+ messages in thread
From: Vincent Li @ 2019-03-29 1:04 UTC (permalink / raw)
To: Tetsuo Handa; +Cc: Linux-MM
On Thu, Mar 28, 2019 at 5:06 PM Tetsuo Handa
<penguin-kernel@i-love.sakura.ne.jp> wrote:
>
> > On Thu, Mar 28, 2019 at 3:46 PM Tetsuo Handa
> > <penguin-kernel@i-love.sakura.ne.jp> wrote:
> > >
> > > 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.
> >
> > I am interested to see OOM output including swap entries per process
> > in swap partition and all
> > the other kernel internal virtual memory stats, I find it useful than
> > top or free or /proc/meminfo
> >
>
> Please read http://man7.org/linux/man-pages/man5/proc.5.html and/or
> https://www.kernel.org/doc/Documentation/filesystems/proc.txt .
Thanks, I know I can get lots of information from /proc/<pid>/, but I
like the format/style that OOM dumps since I
don't have to use some kind of script to parse out the /proc/<pid>,
plus, OOM also dumps node/zone/page orders....information all
together, lots of useful information so I can have big picture on the
memory usage of the system.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-03-29 1:04 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-03-28 21:37 sysrq key f to trigger OOM manually Vincent Li
2019-03-28 22:45 ` Tetsuo Handa
[not found] ` <CAK3+h2wB2x4p976cqA5UPXhz5bZ6mjK98xB8nGQ8hkBoW02k7g@mail.gmail.com>
[not found] ` <201903290006.x2T06fWZ001228@www262.sakura.ne.jp>
2019-03-29 1:04 ` Vincent Li
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.