From: consul.kautuk@gmail.com (kautuk.c @samsung.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1 v4] arm: fault.c: Port OOM changes into do_page_fault
Date: Sat, 19 Nov 2011 22:18:48 -0500 [thread overview]
Message-ID: <CAFPAmTRK6OubP5u_YwcRyyN6vujgqwBaq8-JobdnnYmjEE3Y+g@mail.gmail.com> (raw)
In-Reply-To: <1321181347-4391-1-git-send-email-consul.kautuk@gmail.com>
Hi,
>
> These changes reduce the mmap_sem hold time, which is crucial
> during OOM killer invocation.
>
> Port these changes to ARM.
Did anyone get a chance to look at version 4 of this patch ?
I have incorporated changes as suggested by Russell during version 3 review.
Can I improve this patch in any way ?
>
> Without these changes, my ARM board encounters many hang and livelock
> scenarios.
> After applying this patch, OOM feature performance improves according to
> my testing.
>
next prev parent reply other threads:[~2011-11-20 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 10:49 [PATCH 1/1 v4] arm: fault.c: Port OOM changes into do_page_fault Kautuk Consul
2011-11-20 3:18 ` kautuk.c @samsung.com [this message]
2011-11-22 18:19 ` kautuk.c @samsung.com
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=CAFPAmTRK6OubP5u_YwcRyyN6vujgqwBaq8-JobdnnYmjEE3Y+g@mail.gmail.com \
--to=consul.kautuk@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).