From: Ryan Wang <openspace.wang@gmail.com>
To: rientjes@google.com, mulyadi.santosa@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kernelnewbies@nl.linux.org
Subject: Re: oom killer and long-waiting processes
Date: Fri, 11 Jun 2010 08:34:21 +0800 [thread overview]
Message-ID: <AANLkTinTm1kc1n_GS-nk6t46j1_ia8a8i0H7bHWlmVba@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1006101326440.20197@chino.kir.corp.google.com>
2010/6/11 David Rientjes <rientjes@google.com>:
> On Thu, 10 Jun 2010, Ryan Wang wrote:
>
>> Hi all,
>>
>> I have one question about oom killer:
>> If many processes dealing with network communications,
>> but due to bad network traffic, the processes have to wait
>> for a very long time. And meanwhile they may consume
>> some memeory separately for computation. The number
>> of such processes may be large.
>>
>> I wonder whether oom killer will kill these processes
>> when the system is under high pressure?
>>
>
> The kernel can deal with "high pressure" quite well, but in some cases
> such as when all of your RAM or your memory controller is filled with
> anonymous memory and cannot be reclaimed, the oom killer may be called to
> kill "something". It prefers to kill something that will free a large
> amount of memory to avoid having to subsequently kill additional tasks
> when it kills something small first.
>
> If there are tasks that you'd either like to protect from the oom killer
> or always prefer in oom conditions, you can influence its decision-making
> from userspace by tuning /proc/<pid>/oom_adj of the task in question.
> Users typically set an oom_adj value of "-17" to completely disable oom
> killing of pid (the kernel will even panic if it can't find anything
> killable as a result of this!), a value of "-16" to prefer that pid gets
> killed last, and a value of "15" to always prefer pid gets killed first.
>
> Lowering a /proc/<pid>/oom_adj value for a pid from its current value (it
> inherits its value from the parent, which is usually 0) is only allowed by
> root, more specifically, it may only be done by the CAP_SYS_RESOURCE
> capability.
>
> You can refer to Documentation/filesystems/proc.txt for information on
> oom_adj.
>
Thanks all!
--
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:[~2010-06-11 0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 7:17 Ryan Wang
2010-06-10 16:56 ` Mulyadi Santosa
2010-06-10 20:32 ` David Rientjes
2010-06-11 0:34 ` Ryan Wang [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=AANLkTinTm1kc1n_GS-nk6t46j1_ia8a8i0H7bHWlmVba@mail.gmail.com \
--to=openspace.wang@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mulyadi.santosa@gmail.com \
--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