From: Ingo Molnar <mingo@elte.hu>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, npiggin@suse.de, jdike@addtoit.com,
tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: + mm-invoke-oom-killer-from-page-fault.patch added to -mm tree
Date: Wed, 22 Oct 2008 08:28:02 +0200 [thread overview]
Message-ID: <20081022062802.GF651@elte.hu> (raw)
In-Reply-To: <200810212140.m9LLeq1B026364@imap1.linux-foundation.org>
* akpm@linux-foundation.org <akpm@linux-foundation.org> wrote:
>
> The patch titled
> mm: invoke oom-killer from page fault
> has been added to the -mm tree. Its filename is
> mm-invoke-oom-killer-from-page-fault.patch
>
> Before you just go and hit "reply", please:
> a) Consider who else should be cc'ed
> b) Prefer to cc a suitable mailing list as well
> c) Ideally: find the original patch on the mailing list and do a
> reply-to-all to that, adding suitable additional cc's
>
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
>
> See http://userweb.kernel.org/~akpm/added-to-mm.txt to find
> out what to do about this
>
> The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
>
> ------------------------------------------------------
> Subject: mm: invoke oom-killer from page fault
> From: Nick Piggin <npiggin@suse.de>
>
> Rather than have the pagefault handler kill a process directly if it gets
> a VM_FAULT_OOM, have it call into the OOM killer.
>
> With increasingly sophisticated oom behaviour (cpusets, memory cgroups,
> oom killing throttling, oom priority adjustment or selective disabling,
> panic on oom, etc), it's silly to unconditionally kill the faulting
> process at page fault time. Create a hook for pagefault oom path to call
> into instead.
>
> Only converted x86 and uml so far.
>
> Signed-off-by: Nick Piggin <npiggin@suse.de>
> Cc: Jeff Dike <jdike@addtoit.com>
> Cc: Ingo Molnar <mingo@elte.hu>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
the x86 bits look sane in principle. Needs a lot of testing obviously.
Acked-by: Ingo Molnar <mingo@elte.hu>
a small nit:
> + /*
> + * Give "p" a good chance of killing itself before we
> + * retry to allocate memory unless "p" is current
> + */
> + if (!test_thread_flag(TIF_MEMDIE))
> + schedule_timeout_uninterruptible(1);
comment does not match up the code anymore, we only deal with 'current'
here.
Ingo
parent reply other threads:[~2008-10-22 6:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200810212140.m9LLeq1B026364@imap1.linux-foundation.org>]
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=20081022062802.GF651@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox