public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, kernel-testers@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: 2.6.26-rc5-mm2: OOM with 1G free swap
Date: Wed, 11 Jun 2008 16:11:47 +1000	[thread overview]
Message-ID: <200806111611.47402.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <20080611060029.GA5011@martell.zuzino.mipt.ru>

On Wednesday 11 June 2008 16:00, Alexey Dobriyan wrote:
> On Mon, Jun 09, 2008 at 10:31:45PM -0700, Andrew Morton wrote:
> > - This is a bugfixed version of 2.6.26-rc5-mm1 - mainly to repair a
> >   vmscan.c bug which would have prevented testing of the other vmscan.c
> >   bugs^Wchanges.
>
> OOM condition happened with 1G free swap.

Seems like you've got little or no anon pages left, so 1GB free swap
is no problem (nothing left to page out).


> 4G RAM, 1G swap partition, normally LTP survives during much, much higher
> load.

I would hope it is not a memory leak (which might point to lockless
pagecache). It doesn't look like it because there is still lots of
inactive file pages, so that points to the page reclaim changes
(which is not to say page reclaim changes couldn't cause a memory
leak themselves).

Curious: if you kill off all the LTP tests after the OOM condition,
what does your /proc/meminfo look like before and after running
sync ; echo 3 > /proc/sys/vm/drop_caches

--
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>

  reply	other threads:[~2008-06-11  6:11 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10  5:31 2.6.26-rc5-mm2 Andrew Morton
2008-06-10  6:12 ` 2.6.26-rc5-mm2 Nick Piggin
2008-06-10  7:28 ` 2.6.26-rc5-mm2 Nick Piggin
2008-06-10  8:34   ` 2.6.26-rc5-mm2 Andrew Morton
2008-06-10  8:48     ` 2.6.26-rc5-mm2 Nick Piggin
2008-06-10  9:15       ` 2.6.26-rc5-mm2 Andrew Morton
2008-06-10 12:34         ` 2.6.26-rc5-mm2 Rik van Riel
2008-06-11 18:09       ` 2.6.26-rc5-mm2 Rik van Riel
2008-06-11 23:58         ` 2.6.26-rc5-mm2 Nick Piggin
2008-06-12 19:29           ` 2.6.26-rc5-mm2 Rik van Riel
2008-06-12 21:15             ` 2.6.26-rc5-mm2 (swap_state.c:77) Hugh Dickins
2008-06-13 17:45               ` Rik van Riel
2008-06-13 21:15                 ` Hugh Dickins
2008-06-13 22:03                   ` Rik van Riel
2008-06-10 15:34   ` 2.6.26-rc5-mm2 Lee Schermerhorn
2008-06-10 16:50     ` 2.6.26-rc5-mm2 Hugh Dickins
2008-06-10 10:20 ` 2.6.26-rc5-mm2 lockup up on Intel G33+ICH9R+Core2Duo, -mm1 okay Grant Coady
2008-06-10 18:18   ` Andrew Morton
2008-06-10 21:48     ` Grant Coady
2008-06-10 11:50 ` 2.6.26-rc5-mm2 compile error in vmscan.c Helge Hafting
2008-06-10 12:23   ` Johannes Weiner
2008-06-10 18:37   ` Andrew Morton
2008-06-12  8:13     ` Helge Hafting
2008-06-11  2:26 ` 2.6.26-rc5-mm2 (compile error in mm/memory_hotplug.c) Yasunori Goto
2008-06-11  6:00 ` 2.6.26-rc5-mm2: OOM with 1G free swap Alexey Dobriyan
2008-06-11  6:11   ` Nick Piggin [this message]
2008-06-11  6:15   ` Nick Piggin
2008-06-11  6:27   ` Andrew Morton
2008-06-11  6:31     ` Nick Piggin
2008-06-11  6:36     ` KOSAKI Motohiro
2008-06-11  7:31       ` Frederik Deweerdt
2008-06-11 12:57     ` Rik van Riel
2008-06-11 13:44       ` Nick Piggin
2008-06-11 17:56 ` [BUG] 2.6.26-rc5-mm2 - kernel BUG at arch/x86/kernel/setup.c:388! Kamalesh Babulal
2008-06-11 18:28   ` Dave Hansen
2008-06-11 18:37     ` Vegard Nossum
2008-06-12  6:55       ` Kamalesh Babulal

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=200806111611.47402.nickpiggin@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=kernel-testers@vger.kernel.org \
    --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