[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <28486.1246127726@redhat.com>
Date: Sat, 27 Jun 2009 19:35:26 +0100
From: David Howells <dhowells@...hat.com>
To: Johannes Weiner <hannes@...xchg.org>
Cc: dhowells@...hat.com, Wu Fengguang <fengguang.wu@...el.com>,
"riel@...hat.com" <riel@...hat.com>,
"minchan.kim@...il.com" <minchan.kim@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Christoph Lameter <cl@...ux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
"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>
Subject: Re: Found the commit that causes the OOMs
Johannes Weiner <hannes@...xchg.org> wrote:
> This is from your OOM-run dmesg, David:
>
> Adding 32k swap on swapfile22. Priority:-21 extents:1 across:32k
> Adding 32k swap on swapfile23. Priority:-22 extents:1 across:32k
> Adding 32k swap on swapfile24. Priority:-23 extents:3 across:44k
> Adding 32k swap on swapfile25. Priority:-24 extents:1 across:32k
>
> So we actually have swap? Or are those removed again before the OOM?
That's merely a transient situation caused by the LTP swapfile tests.
Ordinarily, my test machine does not have swap. At the time the OOMs occur
there is no swapspace and the msgctl9 or msgctl11 tests are usually being run.
> The following patch should improve on that.
I can give it a spin when I get home later.
David
--
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