[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A4AC636.4010307@redhat.com>
Date: Tue, 30 Jun 2009 22:13:10 -0400
From: Rik van Riel <riel@...hat.com>
To: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
CC: Wu Fengguang <fengguang.wu@...il.com>,
David Woodhouse <dwmw2@...radead.org>,
David Howells <dhowells@...hat.com>,
Minchan Kim <minchan.kim@...il.com>,
Mel Gorman <mel@....ul.ie>,
Johannes Weiner <hannes@...xchg.org>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Christoph Lameter <cl@...ux-foundation.org>,
"peterz@...radead.org" <peterz@...radead.org>,
"tytso@....edu" <tytso@....edu>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"elladan@...imo.com" <elladan@...imo.com>,
"npiggin@...e.de" <npiggin@...e.de>,
"Barnes, Jesse" <jesse.barnes@...el.com>
Subject: Re: Found the commit that causes the OOMs
KOSAKI Motohiro wrote:
> if my guess is correct, we need to implement #-of-reclaim-process throttling
> mechanism.
There are probably some other things that want throttling,
too.
For example, the number of pages currently under IO can
be as large as the entire file and anon inactive lists,
which can cause page reclaim to fail because none of the
pages are reclaimable yet.
This is probably not a big issue for the page cache,
since the readahead window will collapse before we hit
this problem.
However, we may want to take measures to ensure that
the total number of pages in swap readahead do not
take up the entire inactive anon list - maybe we should
limit it to half that amount, to stay on the safe side?
I'll whip up a patch for this tomorrow.
That should get rid of the OOMs that have been observed
with the swap readahead patches by Johannes.
--
All rights reversed.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists