From: Rik van Riel <riel@redhat.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
akpm@linux-foundation.org
Subject: Re: [RFC][PATCH] prevent incorrect oom under split_lru
Date: Tue, 24 Jun 2008 09:28:24 -0400 [thread overview]
Message-ID: <20080624092824.4f0440ca@bree.surriel.com> (raw)
In-Reply-To: <20080624171816.D835.KOSAKI.MOTOHIRO@jp.fujitsu.com>
On Tue, 24 Jun 2008 17:31:54 +0900
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> if zone->recent_scanned parameter become inbalanceing anon and file,
> OOM killer can happened although swappable page exist.
>
> So, if priority==0, We should try to reclaim all page for prevent OOM.
You are absolutely right. Good catch.
> Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Acked-by: Rik van Riel <riel@redhat.com>
> ---
> mm/vmscan.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> Index: b/mm/vmscan.c
> ===================================================================
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -1464,8 +1464,10 @@ static unsigned long shrink_zone(int pri
> * kernel will slowly sift through each list.
> */
> scan = zone_page_state(zone, NR_LRU_BASE + l);
> - scan >>= priority;
> - scan = (scan * percent[file]) / 100;
> + if (priority) {
> + scan >>= priority;
> + scan = (scan * percent[file]) / 100;
> + }
> zone->lru[l].nr_scan += scan + 1;
> nr[l] = zone->lru[l].nr_scan;
> if (nr[l] >= sc->swap_cluster_max)
>
--
All rights reversed.
--
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:[~2008-06-24 13:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 8:31 KOSAKI Motohiro
2008-06-24 13:28 ` Rik van Riel [this message]
2008-06-25 5:59 ` MinChan Kim
2008-06-25 6:08 ` KOSAKI Motohiro
2008-06-25 6:56 ` MinChan Kim
2008-06-25 6:58 ` MinChan Kim
2008-06-25 7:29 ` KOSAKI Motohiro
2008-06-25 7:37 ` MinChan Kim
2008-06-25 12:11 ` Peter Zijlstra
2008-06-25 13:05 ` MinChan Kim
2008-06-26 1:49 ` Takenori Nagano
2008-06-26 4:37 ` MinChan Kim
2008-06-26 5:24 ` Takenori Nagano
2008-06-26 6:37 ` MinChan Kim
2008-06-26 8:05 ` Takenori Nagano
2008-06-26 0:36 ` 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=20080624092824.4f0440ca@bree.surriel.com \
--to=riel@redhat.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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