public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Phil Oester <kernel@theoesters.com>
Cc: nknight@pocketinet.com, linux-kernel@vger.kernel.org
Subject: Re: 1gb RAM + 1gb SWAP + make -j bzImage = OOM
Date: Sat, 5 Jan 2002 16:17:27 +0100	[thread overview]
Message-ID: <20020105161727.18f04fc3.skraw@ithnet.com> (raw)
In-Reply-To: <20020104172418.A28715@ns1.theoesters.com>
In-Reply-To: <004b01c1955e$ecbc9190$6400a8c0@philxp> <20020104220240.233ae66a.skraw@ithnet.com> <WHITExcPbVzv2N2Ku2000000c76@white.pocketinet.com> <20020104172418.A28715@ns1.theoesters.com>

[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]

On Fri, 4 Jan 2002 17:24:18 -0800
Phil Oester <kernel@theoesters.com> wrote:

> On Fri, Jan 04, 2002 at 04:42:43PM -0800, Nicholas Knight wrote:
> > The one catch is that -j is specified without a number.
> 
> [snip superfluous description of what 'make -j' implies]
> 
> > number, your system is dead. A user issue because it seems the user is 
> > using the option without fully comprehending the consequences.
> 
> eh?  Trust me - i understand the implications of make -j.  It's not an
unreasonable test, especially on a machine with 1gb ram/swap.  For reference,
read Rik's email regarding his reverse VM patch:> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=101007711817127&w=2
> 
> Might be enlightening

I guess this testcase is somewhat driving in the direction of Martins test with
some setis running, meaning it has a lot of standard processes that need files
and try to work out something. Can you try Martins patch at your side, redo the
-j story and give us a result? I attached it for an easy go :-)

Thanks,
Stephan


[-- Attachment #2: vmscan.patch.2.4.17.c --]
[-- Type: text/plain, Size: 1275 bytes --]

--- linux.virgin/mm/vmscan.c	Mon Dec 31 12:46:25 2001
+++ linux/mm/vmscan.c	Thu Jan  3 19:43:02 2002
@@ -394,9 +394,9 @@
 		if (PageDirty(page) && is_page_cache_freeable(page) && page->mapping) {
 			/*
 			 * It is not critical here to write it only if
-			 * the page is unmapped beause any direct writer
+			 * the page is unmapped because any direct writer
 			 * like O_DIRECT would set the PG_dirty bitflag
-			 * on the phisical page after having successfully
+			 * on the physical page after having successfully
 			 * pinned it and after the I/O to the page is finished,
 			 * so the direct writes to the page cannot get lost.
 			 */
@@ -480,11 +480,14 @@
 
 			/*
 			 * Alert! We've found too many mapped pages on the
-			 * inactive list, so we start swapping out now!
+			 * inactive list.
+			 * Move referenced pages to the active list.
 			 */
-			spin_unlock(&pagemap_lru_lock);
-			swap_out(priority, gfp_mask, classzone);
-			return nr_pages;
+			if (PageReferenced(page)) {
+				del_page_from_inactive_list(page);
+				add_page_to_active_list(page);
+			}
+			continue;
 		}
 
 		/*
@@ -521,6 +524,9 @@
 	}
 	spin_unlock(&pagemap_lru_lock);
 
+	if (max_mapped <= 0 && nr_pages > 0)
+		swap_out(priority, gfp_mask, classzone);
+
 	return nr_pages;
 }
 

  reply	other threads:[~2002-01-05 15:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-04 20:32 1gb RAM + 1gb SWAP + make -j bzImage = OOM Phil Oester
2002-01-04 21:02 ` Stephan von Krawczynski
2002-01-05  0:42   ` Nicholas Knight
2002-01-05  1:24     ` Phil Oester
2002-01-05 15:17       ` Stephan von Krawczynski [this message]
2002-01-07  6:22         ` Phil Oester
2002-01-07 14:24           ` Stephan von Krawczynski
2002-01-08  5:11             ` Phil Oester
2002-01-05 21:41       ` Eric W. Biederman
2002-01-05 12:30     ` Luigi Genoni
2002-01-05 15:19     ` Stephan von Krawczynski
2002-01-05 17:57       ` Nicholas Knight
2002-01-06 14:40         ` Stephan von Krawczynski

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=20020105161727.18f04fc3.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=kernel@theoesters.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nknight@pocketinet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox