From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: Kurt Garloff <garloff@kg1.ping.de>
Cc: Linux kernel list <linux-kernel@vger.rutgers.edu>,
Linux MM <linux-mm@kvack.org>
Subject: Re: swap/memory patches
Date: Thu, 22 Oct 1998 22:03:51 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.3.96.981022214651.12636B-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <19981022210251.A948@kg1.ping.de>
On Thu, 22 Oct 1998, Kurt Garloff wrote:
> There have been quite some patches on MM/swap/OOM of Linux by you,
> Andrea and Stephen during the last time. Is there a final version?
> Are there recent (2.1.125+) patches for these problems? Did anything
> get into the kernel?
There are no final versions and nothing got into the kernel.
Personally, I think Andrea's patch (minus the kswapd early
give-up) should go into the kernel now.
My part of the patch (OOM killing when kswapd can't cope
any more _and_ we're really out of memory) is running
well at a lot of people's places, but it really is an added
feature and we're in feature freeze right now.
This feature freeze means that I'm not going to drive Linus
crazy in order to include a feature, not even if 100 sysadmins
have asked me to. If you really really want it in you'll either
have to drive Linus crazy yourself or you'll have to apply the
patch to the kernel yourself -- I will make sure that it's
available...
> What I have in mind, when writing these lines, is:
> (1) cow-swapin: I often observed that after compiling a large C++ program
> (which needs some swap), the shell keeps swapping something in on every
> <Enter> keypress. This is cured by swapoff -a; swapon -a.
> If I correctly understood, this is what cow-swapin was supposed to cure.
Wasn't this fixed -- Andrea, Stephen?
> (2) somebody claimed having found swap bugs
> (3) better oom behaviour
>
> I consider (1) to be a serious bug. I don't know much about (2). (3) is
> obviously hard to solve cleanly.
Several people are running with my solution to (3)
in their kernel and have reported that it kills the
right task 9 out of 10 times. This indicates that
my patch is working rather good...
Rik.
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next parent reply other threads:[~1998-10-22 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19981022210251.A948@kg1.ping.de>
1998-10-22 20:03 ` Rik van Riel [this message]
1998-10-23 10:20 ` Andrea Arcangeli
1998-10-26 14:44 ` 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=Pine.LNX.3.96.981022214651.12636B-100000@mirkwood.dummy.home \
--to=h.h.vanriel@phys.uu.nl \
--cc=garloff@kg1.ping.de \
--cc=linux-kernel@vger.rutgers.edu \
--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