From: Pekka Enberg <penberg@kernel.org>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: rientjes@google.com, akpm@linux-foundation.org,
kamezawa.hiroyu@jp.fujitsu.com, linux-mm@kvack.org
Subject: Re: [patch] mm, oom: force oom kill on sysrq+f
Date: Thu, 23 Feb 2012 20:03:57 +0200 [thread overview]
Message-ID: <CAOJsxLH+2qbshWX3ufFve__ZLu4KAqcaF+3QEkOaGrGaAFbk2w@mail.gmail.com> (raw)
In-Reply-To: <4F467579.3020509@jp.fujitsu.com>
On Thu, Feb 23, 2012 at 7:20 PM, KOSAKI Motohiro
<kosaki.motohiro@jp.fujitsu.com> wrote:
> On 2/22/2012 7:03 PM, David Rientjes wrote:
>> The oom killer chooses not to kill a thread if:
>>
>> - an eligible thread has already been oom killed and has yet to exit,
>> and
>>
>> - an eligible thread is exiting but has yet to free all its memory and
>> is not the thread attempting to currently allocate memory.
>>
>> SysRq+F manually invokes the global oom killer to kill a memory-hogging
>> task. This is normally done as a last resort to free memory when no
>> progress is being made or to test the oom killer itself.
>>
>> For both uses, we always want to kill a thread and never defer. This
>> patch causes SysRq+F to always kill an eligible thread and can be used to
>> force a kill even if another oom killed thread has failed to exit.
>>
>> Signed-off-by: David Rientjes <rientjes@google.com>
>
> I have similar patch. This is very sane idea.
> Acked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Acked-by: Pekka Enberg <penberg@kernel.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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-02-23 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 0:03 David Rientjes
2012-02-23 17:20 ` KOSAKI Motohiro
2012-02-23 18:03 ` Pekka Enberg [this message]
2012-02-25 3:25 ` KAMEZAWA Hiroyuki
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=CAOJsxLH+2qbshWX3ufFve__ZLu4KAqcaF+3QEkOaGrGaAFbk2w@mail.gmail.com \
--to=penberg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.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