All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Rik van Riel <riel@redhat.com>,
	javier@marcet.info, linux-kernel@vger.kernel.org,
	kernel@kolivas.org
Subject: Re: Mem issues in 2.6.9 (ever since 2.6.9-rc3) and possible cause
Date: Tue, 26 Oct 2004 18:01:46 +1000	[thread overview]
Message-ID: <417E046A.5070200@yahoo.com.au> (raw)
In-Reply-To: <20041025151343.7a501719.akpm@osdl.org>

Andrew Morton wrote:
> Rik van Riel <riel@redhat.com> wrote:
> 
>>-		if (referenced && page_mapping_inuse(page))
>>+		if (referenced && sc->priority && page_mapping_inuse(page))
> 
> 
> Makes heaps of sense, but I'd like to exactly understand why people are
> getting oomings before doing something like this.  I think we're still
> waiting for a testcase?

I have found that quite often it is because all_unreclaimable gets set,
scanning slows down, and the OOM killer goes off.

Rik, I wonder if you can put some printk's where all_unreclaimable
is being set to 1, and see if there is any correlation to OOMs?


Aside from that, the patch does make sense, but might be too aggressive.
In heavy swapping loads, the "zero priority" scan might make up a
significant proportion of the scanning done so you'll want to be
careful about regressions there.

  reply	other threads:[~2004-10-26  8:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-23 12:59 Mem issues in 2.6.9 (ever since 2.6.9-rc3) and possible cause Javier Marcet
2004-10-23 19:33 ` Andrew Morton
2004-10-23 23:03   ` Con Kolivas
2004-10-25 21:51 ` Rik van Riel
2004-10-25 22:13   ` Andrew Morton
2004-10-26  8:01     ` Nick Piggin [this message]
2004-10-29 22:39 ` Thomas Gleixner
     [not found] <Pine.LNX.4.44.0410251823230.21539-100000@chimarrao.boston.redhat.com>
2004-10-25 22:33 ` Rik van Riel
2004-10-28 12:06   ` Marcelo Tosatti
2004-10-28 15:27     ` Chris Ross
2004-10-28 15:01       ` Marcelo Tosatti
2004-10-29 13:36     ` Chris Ross
2004-10-29 14:46       ` Chris Ross
2004-10-30  8:25       ` Hiroyuki KAMEZAWA
2004-10-30  8:45         ` Chris Ross
2004-10-30  8:58           ` Hiroyuki KAMEZAWA
2004-10-30  9:30             ` Chris Ross
2004-10-30  9:53               ` Hiroyuki KAMEZAWA
2004-10-30 10:42                 ` Thomas Gleixner
2004-10-31 12:33                   ` Thomas Gleixner
2004-10-30 15:38                 ` Chris Ross
2004-10-29 15:09     ` Thomas Gleixner

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=417E046A.5070200@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=javier@marcet.info \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.