linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Michael L. Galbraith" <mikeg@weiden.de>
To: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
Cc: linux-mm <linux-mm@kvack.org>,
	linux-kernel <linux-kernel@vger.rutgers.edu>
Subject: Re: [PATCH] kswapd fix & logic improvement
Date: Tue, 3 Mar 1998 17:10:28 +0100 (MET)	[thread overview]
Message-ID: <Pine.LNX.3.95.980303161235.2407A-100000@mikeg.weiden.de> (raw)
In-Reply-To: <Pine.LNX.3.91.980303083346.16214A-100000@mirkwood.dummy.home>

On Tue, 3 Mar 1998, Rik van Riel wrote:

> On Tue, 3 Mar 1998, Michael L. Galbraith wrote:
> 
> > I was able to stimulate a 'swap-attack' which took almost a hour to
> > recover control from.
> > 
> > 2.1.89pre5 + swap patch
> 
> To 'recover from' or 'handle' your attack (180+ mb working
> set on an 80 mb machine) is going to need 'real' swapping,
> ie. the temporary suspension of processes to reduce VM load.
> 
> I'd like you to try to even start your stress test under a
> normal kernel (it'll probably work, but not without the
> neccesary oom()s and signal 7s).
> 

I've run much larger working sets on this machine without either
losing control or having the tasks killed. I've run simulations
which ate 400+ Mb. The realtime aspect was a joke, but it worked.

> This patch is only an improvement for normal use. Anyways,
> thrashing can't be combatted by paging algorithms, no matter
> how good.
> 

OK.. thought you wanted it pounded upon.

It was running fine with all tasks being scheduled smoothly until
something triggered a mega-thrash.

> I'll be working on the swapping daemon as soon as I've got
> the current patch sorted out...
> 

Turned out the kswapd messages weren't related to the thrashing.
I would have seen it if I hadn't jumped straight into X.

	-Mike

  reply	other threads:[~1998-03-03 16:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-03  0:35 Rik van Riel
1998-03-03  7:16 ` Michael L. Galbraith
1998-03-03  7:39   ` Rik van Riel
1998-03-03 16:10     ` Michael L. Galbraith [this message]
1998-03-03 17:16       ` Rik van Riel
1998-03-03 19:17         ` Benjamin C.R. LaHaise
1998-03-04  8:33           ` Pavel Machek
1998-03-06  9:06             ` Benjamin C.R. LaHaise
1998-03-06 14:40               ` Pavel Machek
     [not found] <199803031135.MAA19461@max.fys.ruu.nl>
1998-03-03 13:10 ` Rik van Riel

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.95.980303161235.2407A-100000@mikeg.weiden.de \
    --to=mikeg@weiden.de \
    --cc=H.H.vanRiel@fys.ruu.nl \
    --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