From: David Rientjes <rientjes@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Rik van Riel <riel@redhat.com>, Ying Han <yinghan@google.com>,
linux-mm@kvack.org
Subject: Re: [patch 1/3 v3] oom: add per-mm oom disable count
Date: Mon, 23 Aug 2010 17:53:35 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1008231724130.19474@chino.kir.corp.google.com> (raw)
In-Reply-To: <20100823161302.e4378ca0.akpm@linux-foundation.org>
On Mon, 23 Aug 2010, Andrew Morton wrote:
> > --- a/fs/proc/base.c
> > +++ b/fs/proc/base.c
> > @@ -1047,6 +1047,21 @@ static ssize_t oom_adjust_write(struct file *file, const char __user *buf,
> > return -EACCES;
> > }
> >
> > + task_lock(task);
> > + if (!task->mm) {
> > + task_unlock(task);
> > + unlock_task_sighand(task, &flags);
> > + put_task_struct(task);
> > + return -EINVAL;
> > + }
> > +
> > + if (oom_adjust != task->signal->oom_adj) {
> > + if (oom_adjust == OOM_DISABLE)
> > + atomic_inc(&task->mm->oom_disable_count);
> > + if (task->signal->oom_adj == OOM_DISABLE)
> > + atomic_dec(&task->mm->oom_disable_count);
> > + }
>
> scary function. Wanna try converting oom_adjust_write() to the
> single-exit-with-goto model sometime, see if the result looks more
> maintainable?
>
Ok, that would certainly be better.
> > --- a/kernel/fork.c
> > +++ b/kernel/fork.c
> > @@ -65,6 +65,7 @@
> > #include <linux/perf_event.h>
> > #include <linux/posix-timers.h>
> > #include <linux/user-return-notifier.h>
> > +#include <linux/oom.h>
> >
> > #include <asm/pgtable.h>
> > #include <asm/pgalloc.h>
> > @@ -485,6 +486,7 @@ static struct mm_struct * mm_init(struct mm_struct * mm, struct task_struct *p)
> > mm->cached_hole_size = ~0UL;
> > mm_init_aio(mm);
> > mm_init_owner(mm, p);
> > + atomic_set(&mm->oom_disable_count, 0);
>
> So in fork() we zap this if !CLONE_VM? Was the CLONE_VM case tested
> nicely?
>
In clone(), yeah, fork() doesn't use CLONE_VM so the child thread will
always have a different ->mm. The new ->mm will get oom_disable_count
incremented later if tsk has inherited a OOM_DISABLE value.
We've been running with this patch (minus the sys_unshare() code I added)
for a year now internally.
--
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>
next prev parent reply other threads:[~2010-08-24 0:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 22:41 David Rientjes
2010-08-20 22:41 ` [patch 2/3 v3] oom: avoid killing a task if a thread sharing its mm cannot be killed David Rientjes
2010-08-22 9:49 ` KOSAKI Motohiro
2010-08-22 23:14 ` David Rientjes
2010-08-20 22:41 ` [patch 3/3 v3] oom: kill all threads sharing oom killed task's mm David Rientjes
2010-08-20 23:52 ` David Rientjes
2010-08-23 23:16 ` Andrew Morton
2010-08-24 0:57 ` David Rientjes
2010-08-23 23:13 ` [patch 1/3 v3] oom: add per-mm oom disable count Andrew Morton
2010-08-24 0:53 ` David Rientjes [this message]
2010-08-27 21:48 ` Andrew Morton
2010-08-28 22:25 ` [patch] oom: fix locking for oom_adj and oom_score_adj David Rientjes
2010-08-30 4:39 ` [patch 1/3 v3] oom: add per-mm oom disable count KOSAKI Motohiro
2010-08-30 21:14 ` David Rientjes
2010-08-31 23:54 ` KOSAKI Motohiro
2010-09-01 23:41 ` David Rientjes
2010-09-02 0:50 ` KOSAKI Motohiro
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=alpine.DEB.2.00.1008231724130.19474@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=yinghan@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