From: Frederic Weisbecker <fweisbec@gmail.com>
To: Vincent Li <vincent.mc.li@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Don Zickus <dzickus@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
Mandeep Singh Baines <msb@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Softlockup (out of cpu) killer
Date: Mon, 12 Dec 2011 01:28:29 +0100 [thread overview]
Message-ID: <20111212002826.GA23901@somewhere> (raw)
In-Reply-To: <1323643735-1999-1-git-send-email-vincent.mc.li@gmail.com>
On Sun, Dec 11, 2011 at 02:48:55PM -0800, Vincent Li wrote:
> In kernel, there is out of memory (OOM) killer, why not make an out of cpu (OOC) killer?
> I tested following patch by running an user-space cpu hogging process and the softlockukp
> detector killed the process successfully.
>
> Softlockup could be caused by user-space process hogging cpu, add softlockup_kill kernel
> config to allow kernel to kill the user space cpu hogging process. this feature is
> useful for high availability systems that have uptime gurantees and where a softlockup
> must be resolved ASAP
>
> echo 1 > /proc/sys/kernel/softlockukp_kill to enable cpu hog process killer
> echo 0 > /proc/sys/kernel/softlockup_kill to disable cpu hog process killer
That assumes a signal would be enough to pull a process out of its softlockup.
I believe this is seldom the case. A process in a softlockup is stuck in some
place that has preemption disabled. Unless it luckily polls there for pending
signals, that won't work.
But may be that happens more often than I think. May be other people have
more insight.
next prev parent reply other threads:[~2011-12-12 0:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-11 22:48 [PATCH] Softlockup (out of cpu) killer Vincent Li
2011-12-12 0:28 ` Frederic Weisbecker [this message]
2011-12-12 9:38 ` Peter Zijlstra
2011-12-12 18:00 ` 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=20111212002826.GA23901@somewhere \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=msb@chromium.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