From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Nick Piggin <npiggin@suse.de>,
Linux Memory Management <linux-mm@kvack.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/5] oom: don't kill unkillable children or siblings
Date: Fri, 13 Oct 2006 16:31:59 +1000 [thread overview]
Message-ID: <452F32DF.5090608@yahoo.com.au> (raw)
In-Reply-To: <20061012150050.ad6e1c8b.akpm@osdl.org>
Andrew Morton wrote:
>On Thu, 12 Oct 2006 16:09:43 +0200 (CEST)
>Nick Piggin <npiggin@suse.de> wrote:
>
>
>>Abort the kill if any of our threads have OOM_DISABLE set. Having this test
>>here also prevents any OOM_DISABLE child of the "selected" process from being
>>killed.
>>
>>Signed-off-by: Nick Piggin <npiggin@suse.de>
>>
>>Index: linux-2.6/mm/oom_kill.c
>>===================================================================
>>--- linux-2.6.orig/mm/oom_kill.c
>>+++ linux-2.6/mm/oom_kill.c
>>@@ -312,15 +312,24 @@ static int oom_kill_task(struct task_str
>> if (mm == NULL)
>> return 1;
>>
>>+ /*
>>+ * Don't kill the process if any threads are set to OOM_DISABLE
>>+ */
>>+ do_each_thread(g, q) {
>>+ if (q->mm == mm && p->oomkilladj == OOM_DISABLE)
>>+ return 1;
>>+ } while_each_thread(g, q);
>>+
>> __oom_kill_task(p, message);
>>+
>> /*
>> * kill all processes that share the ->mm (i.e. all threads),
>> * but are in a different thread group
>> */
>>- do_each_thread(g, q)
>>+ do_each_thread(g, q) {
>> if (q->mm == mm && q->tgid != p->tgid)
>> __oom_kill_task(q, message);
>>- while_each_thread(g, q);
>>+ } while_each_thread(g, q);
>>
>> return 0;
>>
>
>One wonders whether OOM_DISABLE should be a property of the mm_struct, not
>of the task_struct.
>
Hmm... I don't think I could argue with that. I think this patch is needed
in the meantime though.
--
Send instant messages to your online friends http://au.messenger.yahoo.com
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Nick Piggin <npiggin@suse.de>,
Linux Memory Management <linux-mm@kvack.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/5] oom: don't kill unkillable children or siblings
Date: Fri, 13 Oct 2006 16:31:59 +1000 [thread overview]
Message-ID: <452F32DF.5090608@yahoo.com.au> (raw)
In-Reply-To: <20061012150050.ad6e1c8b.akpm@osdl.org>
Andrew Morton wrote:
>On Thu, 12 Oct 2006 16:09:43 +0200 (CEST)
>Nick Piggin <npiggin@suse.de> wrote:
>
>
>>Abort the kill if any of our threads have OOM_DISABLE set. Having this test
>>here also prevents any OOM_DISABLE child of the "selected" process from being
>>killed.
>>
>>Signed-off-by: Nick Piggin <npiggin@suse.de>
>>
>>Index: linux-2.6/mm/oom_kill.c
>>===================================================================
>>--- linux-2.6.orig/mm/oom_kill.c
>>+++ linux-2.6/mm/oom_kill.c
>>@@ -312,15 +312,24 @@ static int oom_kill_task(struct task_str
>> if (mm == NULL)
>> return 1;
>>
>>+ /*
>>+ * Don't kill the process if any threads are set to OOM_DISABLE
>>+ */
>>+ do_each_thread(g, q) {
>>+ if (q->mm == mm && p->oomkilladj == OOM_DISABLE)
>>+ return 1;
>>+ } while_each_thread(g, q);
>>+
>> __oom_kill_task(p, message);
>>+
>> /*
>> * kill all processes that share the ->mm (i.e. all threads),
>> * but are in a different thread group
>> */
>>- do_each_thread(g, q)
>>+ do_each_thread(g, q) {
>> if (q->mm == mm && q->tgid != p->tgid)
>> __oom_kill_task(q, message);
>>- while_each_thread(g, q);
>>+ } while_each_thread(g, q);
>>
>> return 0;
>>
>
>One wonders whether OOM_DISABLE should be a property of the mm_struct, not
>of the task_struct.
>
Hmm... I don't think I could argue with that. I think this patch is needed
in the meantime though.
--
Send instant messages to your online friends http://au.messenger.yahoo.com
--
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:[~2006-10-13 6:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 14:09 [rfc][patch 0/5] 2.6.19-rc1: oom killer fixes Nick Piggin
2006-10-12 14:09 ` Nick Piggin
2006-10-12 14:09 ` [patch 1/5] oom: don't kill unkillable children or siblings Nick Piggin
2006-10-12 14:09 ` Nick Piggin
2006-10-12 22:00 ` Andrew Morton
2006-10-12 22:00 ` Andrew Morton
2006-10-13 6:31 ` Nick Piggin [this message]
2006-10-13 6:31 ` Nick Piggin
2006-10-12 14:09 ` [patch 2/5] oom: cleanup messages Nick Piggin
2006-10-12 14:09 ` Nick Piggin
2006-10-12 14:10 ` [patch 3/5] oom: less memdie Nick Piggin
2006-10-12 14:10 ` Nick Piggin
2006-10-12 22:03 ` Andrew Morton
2006-10-12 22:03 ` Andrew Morton
2006-10-13 6:38 ` Nick Piggin
2006-10-13 6:38 ` Nick Piggin
2006-10-12 14:10 ` [patch 4/5] mm: incorrect VM_FAULT_OOM returns from drivers Nick Piggin
2006-10-12 14:10 ` Nick Piggin
2006-10-12 14:10 ` [patch 5/5] oom: invoke OOM killer from pagefault handler Nick Piggin
2006-10-12 14:10 ` Nick Piggin
2006-10-12 15:12 ` Kirill Korotaev
2006-10-12 15:12 ` Kirill Korotaev
2006-10-12 15:19 ` Nick Piggin
2006-10-12 15:19 ` Nick Piggin
2006-10-12 22:09 ` Andrew Morton
2006-10-12 22:09 ` Andrew Morton
2006-10-13 6:45 ` Nick Piggin
2006-10-13 6:45 ` Nick Piggin
2006-10-13 6:47 ` Nick Piggin
2006-10-13 6:47 ` Nick Piggin
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=452F32DF.5090608@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.