lkml.org 
[lkml]   [2009]   [Jul]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] copy over oom_adj value at fork time
On Tue, 28 Jul 2009, KOSAKI Motohiro wrote:

> Actually, if we assume the administrator is really stupid, he can mark
> all processes as OOM_DISABLE. it makes livelock anyway.

Wrong, the oom killer will panic the machine if there are no eligible
tasks to kill. That's actually a more desirable result in most
circumstances over livelocking.

> ITOH, we never seen this livelock on vfork()ed application.
>

I have, which is why I wrote my patches.

> More important thing is: Documentation/filesysmtem/proc/txt says
> oom_adj is process property and vfork()ed parent and child are definitelly
> another process.
>

I've proposed adding /proc/pid/oom_adj_child so that newly initialized
mm's start with a default oom_adj value. Paul suggested that it be a
per-task characteristic, so that's what I'm looking at implementing.

Thanks.


\
 
 \ /
  Last update: 2009-07-28 08:17    [W:0.065 / U:0.068 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site