All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Rik van Riel <riel@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>,
	javier@marcet.info, linux-kernel@vger.kernel.org,
	kernel@kolivas.org, barry <barry@disus.com>
Subject: Re: Mem issues in 2.6.9 (ever since 2.6.9-rc3) and possible cause
Date: Thu, 28 Oct 2004 10:06:51 -0200	[thread overview]
Message-ID: <20041028120650.GD5741@logos.cnet> (raw)
In-Reply-To: <Pine.LNX.4.44.0410251833210.21539-100000@chimarrao.boston.redhat.com>

On Mon, Oct 25, 2004 at 06:33:35PM -0400, Rik van Riel wrote:
> On Mon, 25 Oct 2004, Rik van Riel wrote:
> > On Mon, 25 Oct 2004, 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'm now running Yum on a (virtual) system with 96MB RAM and
> > 100MB swap.  This used to get an OOM kill very quickly, but
> > still seems to be running now, after 20 minutes.
> 
> It completed, without being OOM killed like before.

Barry,

Can you please test Rik's patch with your spurious OOM kill testcase?

===== mm/vmscan.c 1.231 vs edited =====
--- 1.231/mm/vmscan.c	Sun Oct 17 01:07:24 2004
+++ edited/mm/vmscan.c	Mon Oct 25 17:38:56 2004
@@ -379,7 +379,7 @@
 
 		referenced = page_referenced(page, 1);
 		/* In active use or really unfreeable?  Activate it. */
-		if (referenced && page_mapping_inuse(page))
+		if (referenced && sc->priority && page_mapping_inuse(page))
 			goto activate_locked;
 
 #ifdef CONFIG_SWAP
@@ -715,7 +715,7 @@
 		if (page_mapped(page)) {
 			if (!reclaim_mapped ||
 			    (total_swap_pages == 0 && PageAnon(page)) ||
-			    page_referenced(page, 0)) {
+			    (page_referenced(page, 0) && sc->priority)) {
 				list_add(&page->lru, &l_active);
 				continue;
 			}


  reply	other threads:[~2004-10-28 14:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0410251823230.21539-100000@chimarrao.boston.redhat.com>
2004-10-25 22:33 ` Mem issues in 2.6.9 (ever since 2.6.9-rc3) and possible cause Rik van Riel
2004-10-28 12:06   ` Marcelo Tosatti [this message]
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
2004-10-23 12:59 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
2004-10-29 22:39 ` 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=20041028120650.GD5741@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=akpm@osdl.org \
    --cc=barry@disus.com \
    --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.