From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: "Michael L. Galbraith" <mikeg@weiden.de>
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 18:16:17 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.980303181105.414D-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <Pine.LNX.3.95.980303161235.2407A-100000@mikeg.weiden.de>
On Tue, 3 Mar 1998, Michael L. Galbraith wrote:
> > 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'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.
When allocation is done piece-by-piece, and there's only
one big process which is faulting all the time, all known
Linux kernels can handle it (more or less).
> > 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.
You were right about that. I wanted to be sure that my
patch was at least as solid as the old code before it
gets merged into the kernel. Judging from the reports
I got, it is. In fact, most people have reported a big
improvement, and some people have pounded and ground it
to a crawl (without being able to make it crash).
> It was running fine with all tasks being scheduled smoothly until
> something triggered a mega-thrash.
Once you start thrashing, only real swapping is an option
to save performance (somewhat).
> > 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.
Ahh, yes. X allocates a _lot_ of memory at once, and then
the damn thing _uses_ it at once... This is guaranteed to
make kswapd a bit nervous, both with or without my patch.
Rik.
+-----------------------------+------------------------------+
| For Linux mm-patches, go to | "I'm busy managing memory.." |
| my homepage (via LinuxHQ). | H.H.vanRiel@fys.ruu.nl |
| ...submissions welcome... | http://www.fys.ruu.nl/~riel/ |
+-----------------------------+------------------------------+
next prev parent reply other threads:[~1998-03-03 19:01 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
1998-03-03 17:16 ` Rik van Riel [this message]
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.91.980303181105.414D-100000@mirkwood.dummy.home \
--to=h.h.vanriel@fys.ruu.nl \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=mikeg@weiden.de \
/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