public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Chip Salzenberg <chip@valinux.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
	Ville Herva <vherva@mail.niksula.cs.hut.fi>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] blindingly stupid 2.2 VM bug
Date: Sat, 25 Nov 2000 14:57:01 +0100	[thread overview]
Message-ID: <20001125145701.A12719@athlon.random> (raw)
In-Reply-To: <20001119100100.A54301@niksula.cs.hut.fi> <Pine.LNX.4.21.0011201135590.4587-100000@duckman.distro.conectiva> <20001124152831.A5696@valinux.com>
In-Reply-To: <20001124152831.A5696@valinux.com>; from chip@valinux.com on Fri, Nov 24, 2000 at 03:28:31PM -0800

+               /* Only lower priority if we didn't make progress. */
+               if (count == loopcount)
+                       --priority;
+               loopcount = count;

If the while loops around the page-recycling-methods were missing we would
have just noticed as soon as we needed to recycle some byte of cache.

+       /* Return success if we have enough free memory or we freed a page. */
+       if (nr_free_pages > freepages.low)
+               return 1;

This anti-kill-flood check is just handled by the GFP layer (you don't
need to replicate it here in the memory balancing layer). It's currently
done against freepages.high to stay conservative (it's meant to catch
a task killed while we were blocked; a task killed will certainly
raise nr_free_pages over freepages.high).

+       return count < SWAP_CLUSTER_MAX;

This will make oom handling less graceful and if memory balancing
fails wrongly when the machine isn't truly oom this will only hide the problem
(and if there's a real problem like we had with MAP_SHARED and
always-async-kpiod [fixed by VM-global] it won't even be enough to hide it).


VM-global-*-7 has no known bugs AFIK.

Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-25 14:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-19  0:04 [PATCH] blindingly stupid 2.2 VM bug Rik van Riel
2000-11-19  8:01 ` Ville Herva
2000-11-20 13:38   ` Rik van Riel
2000-11-24 23:28     ` Chip Salzenberg
2000-11-25 13:57       ` Andrea Arcangeli [this message]
2000-11-25 17:06         ` Rik van Riel
2000-11-28 23:02         ` John Kennedy
2000-11-28 23:20           ` Andrea Arcangeli
2000-11-28 23:36             ` John Kennedy
2000-11-29  0:04               ` Andrea Arcangeli
2000-11-29  0:35                 ` John Kennedy
2000-11-30 11:47                   ` Stephen C. Tweedie

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=20001125145701.A12719@athlon.random \
    --to=andrea@suse.de \
    --cc=chip@valinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=vherva@mail.niksula.cs.hut.fi \
    /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