From: Chris Metcalf <cmetcalf@tilera.com>
To: Kautuk Consul <consul.kautuk@gmail.com>
Cc: <paul.mckenney@linaro.org>,
Lucas De Marchi <lucas.demarchi@profusion.mobi>,
Josh Triplett <josh@joshtriplett.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 15/19 v2] tile/mm/fault.c: Port OOM changes to handle_page_fault
Date: Tue, 3 Apr 2012 12:11:00 -0400 [thread overview]
Message-ID: <4F7B2114.4000806@tilera.com> (raw)
In-Reply-To: <1333195539-5421-1-git-send-email-consul.kautuk@gmail.com>
On 3/31/2012 8:05 AM, Kautuk Consul wrote:
> Commit d065bd810b6deb67d4897a14bfe21f8eb526ba99
> (mm: retry page fault when blocking on disk transfer) and
> commit 37b23e0525d393d48a7d59f870b3bc061a30ccdb
> (x86,mm: make pagefault killable)
>
> The above commits introduced changes into the x86 pagefault handler
> for making the page fault handler retryable as well as killable.
>
> These changes reduce the mmap_sem hold time, which is crucial
> during OOM killer invocation.
>
> Port these changes to tile.
>
> Signed-off-by: Kautuk Consul <consul.kautuk@gmail.com>
> [...]
> + /* No need to up_read(&mm->mmap_sem) as we would
> + * have already released it in __lock_page_or_retry
> + * in mm/filemap.c.
> + */
>
Taken into the tile tree. I adjusted the block comment whitespacing to
normal Linux standard. Thanks!
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next prev parent reply other threads:[~2012-04-03 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 12:05 [PATCH 15/19 v2] tile/mm/fault.c: Port OOM changes to handle_page_fault Kautuk Consul
2012-04-03 16:11 ` Chris Metcalf [this message]
[not found] ` <CAFPAmTTfYKT39gdoKT3P4G2O0xkTSS8g62kKudeLcnpdipzJqg@mail.gmail.com>
[not found] ` <4F7B21FB.3040609@tilera.com>
[not found] ` <CAFPAmTS_2H7BzGndcceBxdnJroy82u++sduCPO2+qxG6-WA=nw@mail.gmail.com>
[not found] ` <4F7B2766.9080208@tilera.com>
[not found] ` <1333471474.26079.43.camel@joe2Laptop>
[not found] ` <4F7B2AA7.5010906@tilera.com>
[not found] ` <1333472391.26079.47.camel@joe2Laptop>
2012-04-03 17:25 ` CodingStyle vs checkpatch for block comments Chris Metcalf
2012-04-03 17:41 ` Joe Perches
2012-04-03 18:08 ` Chris Metcalf
2012-04-03 18:16 ` Joe Perches
2012-04-03 18:27 ` Chris Metcalf
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=4F7B2114.4000806@tilera.com \
--to=cmetcalf@tilera.com \
--cc=consul.kautuk@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=paul.mckenney@linaro.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).